Postgresql: Bad timestamp external representation

Matthew Vanecek mevanecek@yahoo.com
31 Oct 2002 22:17:01 -0600


--=-n0k/rBIfyaVuytlS1pcW
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2002-10-20 at 17:30, John Zoetebier wrote:
> When "Save As" to postgresql database the create database and tables=20
> goes well.
> Immediately thereafter the postgrasql connection stops.
> Error messages in postgresql log:
> -- snip
> ERROR:  Bad timestamp external representation '2002-10-20=20
> 17:37:47.000000 +1300'
> DEBUG:  pq_flush: send() failed: Broken pipe
> -- snip
>=20
> The error dialog box says:
> Can't connect to=20
> /home/johnz/.gnucash/data/postgres:,,localhost,gnucash?username=3Dgnucash
>=20
> Does anybody know a solution?
> Or a workaround?
>=20

Which version of Gnucash?  In CVS (or the 1.7.x series), the whole
architecture has changed and is changing.  I've found the 1.6.x
Postgresql backend somewhat buggy.  I don't think anyone is going to
maintain it going forward.  The 1.8.x series should work well enough, if
you're patient (or have an ultra-fast modern machine), but it is in the
process of redesign.  The redesign may not hit until 2.0, but we'll see.

--=20
Matthew Vanecek
perl -e 'print
$i=3Dpack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
***************************************************************************=
*****
For 93 million miles, there is nothing between the sun and my shadow
except me.
I'm always getting in the way of something...

--=-n0k/rBIfyaVuytlS1pcW
Content-Type: application/DEFANGED-4; name="signature_asc.DEFANGED-4"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA9wgA9OMmiB1jXEBsRAl7FAKCaNlN9kzeSxDf8LDeAbON4mTKpagCfZqr3
QTnfzQrlZgLEy20ow0ZtjwQ=
=spVY
-----END PGP SIGNATURE-----

--=-n0k/rBIfyaVuytlS1pcW--