Re: Date problems with 1.1.17

Federico Di Gregorio wrote:

> > Since  I'm  using  a  "generic" access to database (I mean I have a DB
> > class  which  encapsulate  DB insertion/update/deletion and it doesn't
> > know  about  fields'type) I have to find a general way to resolve that
> > problem.  It would probably be a kind of "case of" on those particular
> > types (MX and datetime).
> then do as Adrian suggested and switch to psycopg 2. psycopg 2
> is pretty stable, unless you try out the async queries.
I feel a bit scary to use psycopg 2: it seems it's still in beta stage 
but I have to release my product on next January...
Anyway I'll take a look at what's the better thing to do (unfortunately 
I even use the dictfetchall and dictfetchone methods that should be 
deprecated in psycopg 2 (right?).
Thanks!

Regards,
 Matteo