On Thu, May 7, 2009 at 11:58 AM, Mariano Martinez Peck < [email protected]> wrote:
> > > 2009/5/7 Hilaire Fernandes <[email protected]> > >> >> 2009/5/7 Mariano Martinez Peck <[email protected]> >> >>> >>> It would be nice you can then confirm me if you are using a TIMESTAMP or >>> a DATETIME. Just to see if that was the problem. >>> >> >> >> Oops sorry, yes it is a timestamp (column named ts). I am not sure but it >> may be a column automatically added by the MySql DB. >> > > > At least we know which is the problem :) > > As I said, the solution (sorry if it isn't good enough) is to use datetime. > Sorry I forgot to said that the supported database types depends of the backend. For example, in MySQL you must use datetime instead of timestamp, but in oracle you can use timestamp. This is not our "limitation" but openDBX one (or even client libraries). All this information is here: http://www.linuxnetworks.de/doc/index.php/OpenDBX/DBMS_Datatypes Cheers, Mariano > > Cheers! > > Mariano > > >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
