Mark Wilson wrote:

> 
> On Thursday, June 19, 2003, at 11:45 AM, Anders Borch wrote:
> 
>> [snip]
> 
> 
>> there are a number of data types that I could not easily port to sql.
>> Booleans for instance, mysql haven't really got a boolean datatype, but
>> dbd_mysql returns the strings "1" or "0" in stead of true and false, so
>> I couldn't store booleans as columns in the same table as the rest of
>> the attributes. I want, like you, to have integers, floats and strings
>> as columns in a table representing a class. Files, booleans, Exceptions
>> (and anything derived from Exception), and Bignums are some of the
>> datatypes I had to treat differently. I put them in separate tables with
>> references to the class table.
>> [snip]
> 
> 
> postgresql has a boolean datatype and supports user-defined datatypes, 
> if you're not locked in to mysql for your application.
> 

For now I'm going for the lowest common denominator for mysql, 
postgresql, and sqlite. So, for now the lowest common denominator is 
what mysql has to offer.

-- 
dc -e 
4dd*od3*dddn1-89danrn10-dan3+ann6*dan*2*an13dn1+dn2-dn3+5*ddan2/9+an13nap