pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Richard Broersma <richard.broersma@gmail.com>
To: PostgreSQL - General ML <pgsql-general@postgresql.org>
To: pgsql-odbc@postgresql.org
Subject: what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
Date: Tue, 10 Jun 2008 21:06:13 -0700
Message-ID: <396486430806102106i4915845ag746566c333bdc684@mail.gmail.com> (raw)

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



view thread (4+ messages)  latest in thread

Message-ID: <396486430806102106i4915845ag746566c333bdc684@mail.gmail.com>
Permalink:  ../396486430806102106i4915845ag746566c333bdc684@mail.gmail.com/
Also on:    postgresql.org/message-id/396486430806102106i4915845ag746566c333bdc684@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: richard.broersma@gmail.com, pgsql-general@postgresql.org, pgsql-odbc@postgresql.org
  Subject: Re: what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
  In-Reply-To: <396486430806102106i4915845ag746566c333bdc684@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox