[DB-SIG] DB-API Spec. 1.1a1

[raf]

[apologies to the one who got this twice]

>Bill Tutt wrote:
>> 
>> The "best way" for date/time formats is easy.. DON'T
>> The reason you don't want to do this is because it imposes an uncessary
>> requirement on the code that works with the database i.e. dealing with
>> different date formats.. Thats just silly.

it's also silly to impose a uniform time/date type on the time/date
values across ALL databases IF such a type were to cause information
loss. the sybase datetime datatype consists of 2 four byte integers.
if that gets converted into something like a double or a unix-datetime
(seconds since 1970) then the data has been corrupted. other databases
probably have precise datetime types as well. if ONE type is to be used,
it cannot be allowed to lose information under any circumstances.

if this is impossible or would cause inefficiency when dealing with less
demanding databases, then the dbimodule should only specify an interface,
not a representation. that would have to be left to the modules that
specialise it.

raf



_______________
DB-SIG  - SIG on Tabular Databases in Python

send messages to: db-sig@python.org
administrivia to: db-sig-request@python.org
_______________