On Tue, Nov 7, 2017 at 10:11 AM, Vernon D. Cole wrote:
> Obviously Bob has found a where a value an internal form blows up when fed
> directly back into an INSERT. I suspect that if his row.date value was run
> through a real datetime object that things would magically
On Tue, Nov 7, 2017 at 10:49 AM, Dennis Lee Bieber
wrote:
> >> When running under Python 2.7.13, the first print statement shows that
> >> the datetime value has been correctly retrieved, preserving the
> >> precision:
> >>
> >> d=2017-11-04 07:52:18.11
> >>
>
The real question here is where the significance gets lost. It's hard to
get a handle on what is really in the tables. Also, the time conversion
routines (both in and out of the database) are a mass of confusion.
Obviously Bob has found a where a value an internal form blows up when fed
directly