David Dabney wrote:
The more I thought about this I realized it's not a bug and I'm sorry to
have perstered the list. The fact that the data logger was deployed
before and after a time change and it was not setup to update itself
created this problem. I just have to push forward all the times
The more I thought about this I realized it's not a bug and I'm sorry to
have perstered the list. The fact that the data logger was deployed
before and after a time change and it was not setup to update itself
created this problem. I just have to push forward all the times after
the change an
Tom,
Thanks for the quick reply and I'm sorry I wasn't explicit enough in my
description. At the top of the attachment there is this section which
is the piece of data from DD5 that is causing the problem:
MS Access Details:
DATA TO IMPORT FROM LOCAL MSACCESS Table into lin
"David Dabney" <[EMAIL PROTECTED]> writes:
> I'm assuming this is a bug.
Perhaps, but there is absolutely no chance of anyone reproducing the
problem from the information you've offered. You say "it fails when
I try to insert data from table DD5", but you give us no clue about
what data is in DD5
I'm sorry, but I attached the incorrect file the first time!
We are using MS Access as a frontend to import many water quality records into
postgresql v. 8.0.2 on Red Hat 3 Enterprise.
When importing a table of 40,000+ records something is going wrong with the
timestamp field only for certain re
