Sameer N Ingole wrote:
> Hans Lellelid wrote:
>> You don't neeed to specify default="Null", since that is the default
>> for any non-required column. It looks like the reverse engineering
>> thing is getting the case wrong. Try "NULL" and see if that fixes it
>> (or just remove the default="Null" attribute).
> Tried removing default="whatever" and <parameter name="Default"
> value="whatever"/> but still getting same error.
>
> This is happening only when I try to build using schema.xml
> automatically created by propel-gen from our existing database. If I use
> different schema.xml, it works. I tried it with just one table def
> containing datetime/timestamp. It will take a long time as I have approx
> 80 tables in that database many tables containing over 12 columns..
>
Are you sure you're getting the *same* error after modifying schema.xml
(and rebuilding everything)? That doesn't make a lot of sense, since
the error is definitely complaining about trying to make 'Null' a
date/time value... So, I would suggest that you make sure that you
don't have any default="" for your date/time columns.
Hans
|
