Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [GENERAL] what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
- From: "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com>
- To: "Richard Huxton" <dev(at)archonet(dot)com>
- Cc: "PostgreSQL - General ML" <pgsql-general(at)postgresql(dot)org>, pgsql-odbc(at)postgresql(dot)org
- Subject: Re: [GENERAL] what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
- Date: Wed, 11 Jun 2008 05:32:45 -0700
- Message-id: <396486430806110532i23e211d0ta3059e30f927927d@mail.gmail.com> <text/plain>
On Wed, Jun 11, 2008 at 12:07 AM, Richard Huxton <dev(at)archonet(dot)com> wrote: >> 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 > > That appears to be a deliberate bad query issued by something (above the > odbc layer?). I think you've got something sending "SELECT INVALID SELECT > STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE" as a query to force a > rollback. Why it's not just sending "ROLLBACK" I don't know. I see that makes sense. At least knowing this will help me to trouble shoot where to go from here. -- Regards, Richard Broersma Jr. Visit the Los Angles PostgreSQL Users Group (LAPUG) http://pugs.postgresql.org/lapug
- References:
- Prev by Date: "No Mapping exists" Error
- Next by Date: wrong value returned?
- Previous by thread: Re: [GENERAL] what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
- Next by thread: "No Mapping exists" Error
- Indexes: