Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 7 of 7 total
Thread Timestamp in Stored Procedure
Wed, Apr 18 2007 7:02 PMPermanent Link

"Lance R"
It doesn't like my timestamp insertion.  I've tried it every which way but
the right way... lol.
All qoutes except around taddresstype are single quotes.

Lance



  EXECUTE IMMEDIATE 'INSERT INTO "taddresstype" VALUES (
  ''{2AD33F4D-D9B0-40FD-AFAF-7A3EE8C1B1EF}'',
  ''Billing'',
  ''2007-04-17 12:00'',
  ''2007-04-17 12:00'',
  True,
  3)';



Thu, Apr 19 2007 3:52 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Lance

How about fully defining the time portion eg 2007-04-17 12:00:00.000?

Roy Lambert
Thu, Apr 19 2007 1:06 PMPermanent Link

"Lance R"
Roy,

I thought I tried it, but I'll try again.

I thought by the help that it could be either/or.

Thanks

Lance



"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:EE8735EA-0E40-4178-BAFE-A3617E822E19@news.elevatesoft.com...
> Lance
>
> How about fully defining the time portion eg 2007-04-17 12:00:00.000?
>
> Roy Lambert
>

Thu, Apr 19 2007 6:15 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Lance,

<< It doesn't like my timestamp insertion.  I've tried it every which way
but the right way... lol. All qoutes except around taddresstype are single
quotes. >>

You need to preface the timestamp constants with the keyword TIMESTAMP.  See
this here for more information:

http://www.elevatesoft.com/edb1sql_date_time_types.htm

under "Literals".

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Apr 19 2007 7:41 PMPermanent Link

"Lance R"
I see.....   said the blind man...

Thanks!

Lance

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:811FD1FE-DCC8-4330-B492-E68DF11CDC93@news.elevatesoft.com...
> Lance,
>
> << It doesn't like my timestamp insertion.  I've tried it every which way
> but the right way... lol. All qoutes except around taddresstype are single
> quotes. >>
>
> You need to preface the timestamp constants with the keyword TIMESTAMP.
> See this here for more information:
>
> http://www.elevatesoft.com/edb1sql_date_time_types.htm
>
> under "Literals".
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Mon, Apr 23 2007 4:17 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Lance,

<< I see.....   said the blind man... >>

For the record, I really didn't want to change date/time constants again for
EDB, but it's a standard thing and I felt that it would be best to stick
with the standard, especially with the introduction of date/time interval
types.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Apr 23 2007 6:25 PMPermanent Link

"Lance R"
That's your story and your sticking to it....  grin.

I understand.  I would prefer to stick with the standard as well.

Lance


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:44C1FBA7-142B-44E4-A7BF-D19896BB332A@news.elevatesoft.com...
> Lance,
>
> << I see.....   said the blind man... >>
>
> For the record, I really didn't want to change date/time constants again
> for EDB, but it's a standard thing and I felt that it would be best to
> stick with the standard, especially with the introduction of date/time
> interval types.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Image