To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115384
------- Additional comments from lu...@openoffice.org Thu Nov 25 18:17:38 +0000 2010 ------- Had a look at dba34b: #i115384# check if the length of BIT > 1 otherwise use setBoolean, and change typeinfo for ado types. Although I don't understand all changes I wanted to share a few comments: 1) ADOS::MapADOType2Jdbc doesn't produce any DataType::BIT anymore. adBoolean is translated to DataType::BOOLEAN. This alone would solve the original problem. The case DataType::BIT: in copytablewizard doesn't occur anymore when copying from ADO tables. 2) From your comments regarding Access reporting size 2 for adBoolean I fear that the number of bits and the byte representation gets mixed up. Access uses 2 bytes internally for a single Yes/No value. Hence, it reports size 2. It doesn't know multiple bit values. MySQL on the other hand knows multiple bit fields and will return up to 8 bytes to represent up to 64 bits. Using ODBC a MySQL BIT(1) and a BIT(5) field will return size 1, a BIT(31) field will return size 4, etc. However, only BIT(1) will return the SQL_BIT type (MySQl Connector ODBC 5.1). Multiple bit fields return SQL_BINARY. So, I don't know what database/interface source would cause a positive test BIT>1. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
