Re: timestamp parse error

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'samuele(dot)brignoli(at)darpha(dot)com'" <samuele(dot)brignoli(at)darpha(dot)com>, "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>, pgadmin-support(at)postgresql(dot)org
Subject: Re: timestamp parse error
Date: 2002-03-20 22:21:42
Message-ID: FED2B709E3270E4B903EB0175A49BCB10476D6@dogbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

pgAdmin converts timestamps to the format:

'2001-12-04 00:00:00'

A quick test of this format:

helpdesk=# create table ts(ts1 timestamp);
CREATE
helpdesk=# insert into ts values('2001-12-04 00:00:00');
INSERT 408834 1

A test of the format in your query:

helpdesk=# insert into ts values('2001-12-04 00:00:00.0');
INSERT 408835 1

Regards, Dave.

> -----Original Message-----
> From: Samuele Brignoli [mailto:samuele(dot)brignoli(at)darpha(dot)com]
> Sent: 20 March 2002 17:00
> To: Henshall, Stuart - WCP; pgadmin-support(at)postgresql(dot)org
> Subject: R: [pgadmin-support] timestamp parse error
>
>
>
> The problem is that I was trying to use the great tool that
> port a db from a SQL server db to a Postgresql one. I don't
> have control on the query, maybe I could change the data. But
> my datas in db are standard date/time for SQL server ( I've
> checked also the locale, it's English ). The question is :
> Does PGAdmin makes some manipulation of date/time data before
> generating the query ? 'Cause Postgresql does'n support that
> standard 00.00.00. I'm stopped in the middle of a great
> porting so I'm very sad. Can we try talking to those guys
> that makes the plug-in ?
>
> Thanks Stuart --- Samuele.
>
> -----Messaggio originale-----
> Da: pgadmin-support-owner(at)postgresql(dot)org
> [mailto:pgadmin-support-owner(at)postgresql(dot)org]Per conto di
> Henshall, Stuart - WCP
> Inviato: venerdì 25 gennaio 2002 13.40
> A: 'samuele(dot)brignoli(at)darpha(dot)com'; pgadmin-support(at)postgresql(dot)org
> Oggetto: Re: [pgadmin-support] timestamp parse error
>
>
> It doesn't know this is a timestamp so I guess it sees 00 and
> tries to read as a number. to get it to work try putting it
> in appostraphes. This should make it of type text. If this
> isn;t automatically cast then us the following (assuming its
> a timestamp): CAST ('2001-12-04 00:00:00.0' AS timestamp)
> - Stuart
>
> > -----Original Message-----
> > From: Samuele Brignoli [mailto:samuele(dot)brignoli(at)darpha(dot)com]
> > Sent: 25 January 2002 10:50
> > To: pgadmin-support(at)postgresql(dot)org
> > Subject: [pgadmin-support] timestamp parse error
> >
> >
> > I'm trying to execute this :
> >
> > insert into
> > ahepatch(cpccchk,ptcodrel,ptdatins,ptdescri,ptnumpat,ptreleas)
> > values ('kfdujcqkgp','1.02-A0001',2001-12-04
> 00:00:00.0,'Aggiornamento
> > EURO-KIT',1,'1.2');
> >
> > I obtain an error :"Parse error near or at "00".
> >
> > What is the problem ? The form 00:00:00.0 is contemplated
> ... or not
> > ?!
> >
> > --kako
> >
> >
> > ---------------------------(end of
> > broadcast)---------------------------
> > TIP 3: if posting/reading through Usenet, please send an
> appropriate
> > subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> > message can get through to the mailing list cleanly
> >
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an
> appropriate subscribe-nomail command to
> majordomo(at)postgresql(dot)org so that your message can get through
> to the mailing list cleanly
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
http://www.postgresql.org/users-lounge/docs/faq.html

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Samuele Brignoli 2002-03-21 08:20:34 R: timestamp parse error --- *** Migration PLUG-IN ***
Previous Message Revista Educao 2002-03-20 22:14:28 Revista Educao