On Thu, 2006-01-12 at 22:41 +0100, Markus Hoenicka wrote: > Hi Jeremy, > > are you using the libdbi-0.8.1 sources? A similar problem has been > reported before by Sami Tolvanen, see: > > http://sourceforge.net/mailarchive/forum.php?thread_id=9174478&forum_id=33788 > > This problem has been fixed in the CVS version. Could you please check > out the CVS version and see whether this eliminates your problem?
Marcus, I am sorry I have not had the time yet to try the CVS copy. It does indeed look like my bug report is a duplicate though, and that the fix will correct the code. I, however, have another report :-( ... Most of my database fields are reporting a postgresql type as PG_TYPE_NUMERIC, which is decimal 1700. In _translate_postgresql_type ... PG_TYPE_NUMERIC is never addressed. In fact, the PG_TYPE_FLOAT4 type, I cannot get postgresql to produce. Anything I seem to type in for a field type of decimal or numeric, always produces PG_TYPE_NUMERIC. For the fun of it, I added case PG_TYPE_NUMERIC right above the PG_TYPE_FLOAT4 and all worked, however, again, I am not sure if that's the correct fix. I see the DBI_DECIMAL_SIZE4 and am not totally sure what that is. I will be trying the CVS copy of libdbi real soon. Thanks! Jeremy ------------------------------------------------------- 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 _______________________________________________ libdbi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libdbi-devel
