From: | Timothy(dot)Oliver(at)worldspan(dot)com |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | postgres sql 7.1.1 |
Date: | 2003-04-18 17:28:20 |
Message-ID: | OF3718B48D.007F6DBC-ON85256D0C.005FF7AD-85256D0C.005FFAED@worldspan.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I'm running into problems with a function on the development Postgres
database server. This function works fine on the production database
server, but returns an error when executed using PGAdmin or within code. I
can't say that we've ever attempted to run this function in our
development/preproduction environments before, since we haven't needed to
troubleshoot the "PNRParser" code this much before.
When I try to run the following statement:
select
create_new_airline_itinerary(693666,'DL','1111','Y','ATL','MCI','2003-04-27
15:54:00','2003-04-27 19:54:00','HK1','NW','2222','Y')
I get the error message:
Error: ERROR: parser: parse error at or near "$9" (State:HY000,
Native Code: 7)
I though the error might be related to the minor difference between the
function on the production and development Postgres servers (the 7 and 8
parameters are declared as "timestamptz" on development and preprod but
just "timestamp" on the production database server). I created a new
function "create_n_itin" that looks exactly the same as the function on
production, but the same error occurs when I execute this function.
Any ideas why this Postgres function is failing? I don't know what it
thinks is wrong with the 9th parameter!
Tim Oliver
Senior Database Analyst
Worldspan
300 Galleria Parkway, NW
Mail Stop N11A5
Atlanta, Georgia 30339
(770)563-2508
timothy(dot)oliver(at)worldspan(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Slag | 2003-04-18 22:06:55 | 7.1 -> 7.3 migration timestamp problem |
Previous Message | Timothy.Oliver | 2003-04-18 17:22:27 | postgres sql 7.1.1 |