/ gustavsenska's Library/ Notes/ Little Known Questions About From: Alan Pinstein [e-mail redacted]] Sent: Friday, September.
Little Known Questions About From: Alan Pinstein [e-mail redacted]] Sent: Friday, September.
from web site
How [libRETS-users] Memory leak in GetObject (revisited) - Google can Save You Time, Stress, and Money.
PEMCO Realty Managing Broker Claxton Real Estate, Inc. Broker/Owner Century 21 Real Estate LLC Organization Expert Keller Williams Real Estate Peachtree Roadway.
Aha you simply discovered the bug! I changed from "creole" to "reverse"! I just compared the output of both schema files, and the "reverse" target produces a VARCHAR not a TIMESTAMP. This is a postgresql database. I am utilizing "timestamptz" columns. I included the following to database/reverse/pgsql/ 57 'timestamp' => Propel, Types:: TIMESTAMP, 58 'timestamptz' => Propel, Types:: TIMESTAMP, *** ADDED *** 59 'tinyblob' => Propel, Types:: BINARY, Which made it work.
Possibly you likewise require to include one for "timetz"? I am not 100% confident of my understanding of this problem, so I'll let you implement the precise information, but I believe we've discovered the bug. Thanks! This Author On Feb 27, 2008, at 6:10 PM, Hans Lellelid wrote: Hi Alan, I'm confused; I see it's a timestamp in your database, but it looks like a varchar in your schema.
How CORRECTING and REPLACING - Canadian Insider can Save You Time, Stress, and Money.
did something change there? Alan Pinstein composed: Alan Pinstein wrote: When using beta3, the following code worked: $obj- > set, Dts( time() ); Whereas in beta4, it broke, and had to be converted to: $this- > set, Dts( date(' r') ); Can someone please discuss what occurred? I do not necessarily mind it, but I have looked through the code and the wiki and there is no explanation of temporal * mutator * habits, just temporal * accessor * habits.
There was a system test testing this-- and now I just included a couple more assertions so that we're testing not just time columns, but also timestamp and date columns. This is passing fine. I can quickly reproduce the bug. Not able to execute INSERT statement. [covered: SQLSTATE: Void datetime format: 7 MISTAKE: void input syntax for type timestamp with time zone: "1204153379"] and, from propel.
Can you examine whether you have actually set: move. use, Date, Time, Class = real That ought to be the default, and shouldn't really impact the results here, but is the only thing I can consider straight off. I don't have it set to incorrect, and I likewise attempted it with the specific setting (it didn't alter the code, so the default was properly working).
