Wow, Mike you are having an amazingly productive weekend - I can barely keep up
with the timeline, let alone the actual code changes. Do you have a replacement
keyboard handy!!
WRT to the float/type changes in rev669 and your question on Ticket#14 "I do
notice, running the engine test suite, that the float type Postgres converts it
to a Real of precision 24, and MySQL converts it to precision 12"
What version of Postgres are you running? I'm running 8.02 and it is creating
float4 columns for the engine.py test tables which, according to the postgres
doco, are 'reals' with 6 decimal digits precision, while float8's/double
precision have 15 decimal digits precision.
As far as a type for bigInt, is it necessary to have a separate type, as long as
the postgres module can map it to an Integer that should be sufficient (a bigInt
can range from -9223372036854775807 to +9223372036854775807, which Python should
be able to handle, i.e. int () will automatically return a long if the value is
too large for a std Python integer). Is there something I'm missing?
Robert
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
