Re: Cheap (or open source) RDB for Windows compatible with WO ...

Have not been bitten by this.... but I did a little experimenting to 
decide whether I should use database defaults or initialize my defaults 
in my EO's when they are first created. The answer is simply to use 
NULL as default since that is what EOF does, or if you are going to 
have zero as a default for example in the DB, then make sure the EO 
initializes the same attribute as zero when it is created. Otherwise 
the EOF "snapshot" will not match what was written tom the database and 
you will get an exception when you save.

More on this here:
http://homepage.mac.com/kelleherk/iblog/C729512539/index.html

On Feb 25, 2004, at 4:11 AM, Dirk Olmes wrote:

>> So far, I like MySQL, it's free, very fast, and its "shortcomings" may
>> indeed be features that you do not need when the sophisticated EOF in
>> WO is controlling it with standard ANSI SQL 92.
>
> Well, I can't second that opinion. Ever been bitten by the famous
> default-value-for-not-null-columns "feature"?  I didn't invest any more
> energy in finding out why EOF leaves out columns on insert but moved 
> all
> of my databases to PostgreSQL. Happy ever since :-)
>
> In terms of support, I like the MySQL Windows tools better but postgres
> tools seem to catch up. One thing that really sucks about PostgreSQL 
> ist
> the need for VACUUMs, even if you can do it in parallel to normal
> operations now.
>
> -dirk
>
>
> _______________________________________________
> EOF mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/eof
>




___________________________________
Kieran Kelleher
Director of Product Development
SmartleadsUSA,LLC
2656 West Lake Rd
Palm Harbor, FL 34684
[email protected]
727-785-0766 x33