Raúl Rodriguez <[EMAIL PROTECTED]> writes: > Hi All! Well i think that i can define a bit more detailed > description of the bug. The main problem is not that that a fail > Deserialization gives a Segment Violation (thank you for fix that > also), is that que receive and Deserialization error without a > reason aparently. I made more test to determine the problem, and the > problem persist with bigint type only and Carob, with JDBC and > Sequoia the error doesn't appear. This is an example to > reproduce the error: CREATE TABLE temp ( > id bigint(20) unsigned, dest varchar(25) > ); INSERT INTO temp VALUES (1507,"666"); > SELECT id FROM temp WHERE dest='666'; In this last "SELECT", > Carob complains about a Deserialization error, thing that not happen > with JDBC/Sequoia or if a define id in the table temp like "int". I > hope it can help to determine the problem. Thank you in > advance.
Thanks a lot for the report. From what you say, it seems that MySQL connector/J is returning a non-JDBC java object when calling .getObject(col) on a bigint(20) column. Could you please check that? This should be just the matter of printing: .getObject(col).getClass().getName() You can also try again using the latest carob code in CVS; I just added more specific exception messages. Thanks in advance! As opposed to the JDBC driver, Carob is currently compatible only with JDBC objects (not "java" but JDBC). Changing this is not currently on the roadmap, especially for product-specific objects. Cheers, Marc _______________________________________________ Carob mailing list [email protected] https://forge.continuent.org/mailman/listinfo/carob
