Skip site navigation (1) Skip section navigation (2)

what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE

From: "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com>
To: "PostgreSQL - General ML" <pgsql-general(at)postgresql(dot)org>, pgsql-odbc(at)postgresql(dot)org
Subject: what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
Date: 2008-06-11 04:06:13
Message-ID: 396486430806102106i4915845ag746566c333bdc684@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-generalpgsql-odbc
Server logs below.  Notice how an error raised in a connection to the
proj02u20411 database forces the transaction in the instrumentation
database to rollback.
Can anyone explain why connections that as far as PG should conserned
are unrelated are actually interferring with one another?
--------------------------------------------------------------------------------

2008-06-10 15:04:51instrumentation LOG:  statement:
                  BEGIN;
                  INSERT INTO Dev.Tagables( devicecode )
                         VALUES ( E'PROCESS SWITCH' )
                    RETURNING tagableid;
2008-06-10 15:04:52instrumentation LOG:  statement:
                  INSERT INTO Dev.Instrumentassemblies( partnbr,
                                             equipmentnbr, tagableid,
                                             devicecode, manufacture,
                                             fundedby, purchasedby )
                        VALUES( E'1140-181-201-D', E'RW-0184-402.02',
                                       1, E'PROCESS SWITCH',
                                       E'HAMON RESEARCH COTTRELL',
                                       E'02U20410', NULL );
2008-06-10 15:04:52instrumentation LOG:  statement:
                  INSERT INTO Dev.SignalingDevices( tagableid, devicecode )
                        VALUES( 1, E'PROCESS SWITCH' );
2008-06-10 15:04:52instrumentation LOG:  statement:
                  INSERT INTO Dev.Switches( tagableid, devicecode )
                        VALUES( 1, E'PROCESS SWITCH' );
2008-06-10 15:04:52instrumentation LOG:  statement:
                  INSERT INTO Dev.Loopcontainment( endprojectnbr, area,
                                             pcode, loopnbr, loopsuf,
                                             tagableid, instrumentcode,
                                             instrumentsuff, startprojectnbr )
                  VALUES( E'AS-BUILT', 84, E'L', 3117, E'', 1, E'LSL',
                                 E'', E'02U20410' );
2008-06-10 15:04:52instrumentation LOG:  statement:
                  INSERT INTO Dev.Tags( instrumentcode, instrumentsuff,
                                                      area, loopnbr, hasbackup,
                                                      endprojectnbr,
"p&idsection" )
                  VALUES( E'LSL', E'', 84, 3117, '0', E'AS-BUILT', 14 );
2008-06-10 15:04:52proj02u20411 LOG:  statement:
                  SELECT "rid" ,"mid" ,"pid"
                     FROM "dev"."rtl_tagnr_mat_purch"
                  WHERE ("rid" = NULL)
2008-06-10 15:04:52proj02u20411 LOG:  statement:
                  SELECT "itid" ,"itcode"
                    FROM "dev"."insttype"
                 WHERE ("itid" = 58)
2008-06-10 15:04:52proj02u20411 LOG:  statement:
                  SELECT "vid" ,"name"
                     FROM "dev"."vendor"
                  WHERE ("vid" = NULL)
2008-06-10 15:04:52proj02u20411 LOG:  statement:
                  SELECT "cid" ,"designation"
                     FROM "equ"."component" "CA"
                  WHERE ("cid" = NULL)
2008-06-10 15:04:52proj02u20411 LOG:  statement:
                  SELECT "sid" ,"sectno"
                     FROM "docs"."section"
                  WHERE ("sid" = 40)
2008-06-10 15:04:52proj02u20411 LOG:  statement:
                 SELECT "cid" ,"designation"
                    FROM "equ"."component" "CB"
                 WHERE ("cid" = NULL)
2008-06-10 15:04:52instrumentation ERROR:  syntax error at or near
"SELECT" at character 16
2008-06-10 15:04:52instrumentation STATEMENT:  SELECT INVALID SELECT
STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
2008-06-10 15:04:52instrumentation LOG:  statement: ROLLBACK

-- 
Regards,
Richard Broersma Jr.

Visit the Los Angles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

Responses

pgsql-odbc by date

Next:From: Richard HuxtonDate: 2008-06-11 07:07:28
Subject: Re: what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
Previous:From: Hiroshi InoueDate: 2008-06-11 00:57:08
Subject: Re: Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons

pgsql-admin by date

Next:From: Praveen Kumar (TUV)Date: 2008-06-11 06:14:44
Subject: Re: Disk Space issue
Previous:From: Tom LaneDate: 2008-06-11 01:28:37
Subject: Re: Disk Space issue

pgsql-general by date

Next:From: Sim ZacksDate: 2008-06-11 05:35:59
Subject: Re: encoding confusion
Previous:From: Tom LaneDate: 2008-06-10 23:17:37
Subject: Re: Large objects oids

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group