Hi! Check that a row in Pharo's OpenDBX driver answers to: - #values it reads the value from the database and tries to convert it to the corresponding object representation (e.g., a mysql date to a pharo date) - #rawValues it returns a string representing the direct representation in mysql. So maybe if you use #rawValues you can query the database and do whatever you want with the "unparsed" value. Tell us if this helps you! Guille On Thu, Oct 23, 2014 at 3:40 AM, bsselfridge@gmail.com < bsselfridge@gmail.com> wrote:
Yes, the column type definition is: timestamp.
I am trying to use Pharo to access some old legacy MySQL tables. These tables have "timestamps" defined everywhere and there is NO WAY I will be allowed to change them. So, I'm going to have to try to figure out how to get around this problem.
Since I'm new to the Pharo camp, (old VASmalltalk'er using DB2 as database), do you think the OpenDBX people would be open to supporting timestamp in their library?
Brad Selfridge
----- Brad Selfridge -- View this message in context: http://forum.world.st/Pharo-OpenDBXDriver-Unsupported-data-type-UNKNOWN-tp47... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.