Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Interfaces Odbc > Re: Re: " for r...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 6 of 8 Topic 2306 of 2387
Post > Topic >>

Re: Re: " for read only" clause appended for safety when UseDeclareFetch=1

by alepaes@[EMAIL PROTECTED] (alepaes - aldeia digital) Jun 10, 2008 at 11:45 AM

Hi,

Postgresql 8.2.3 have the same problem:

<192.168.1.10>ERROR:  syntax error at or near "read" at character 487
<192.168.1.10>STATEMENT:  declare "SQL_CUR01B5BDE8" cursor for  SELECT 
ct12emp04, ct12numlot, ct12numlan, ct12dtlanc, ct12do***e, ct12empcc1, 
ct12empcc2,   ct12empcc3, ct12emptr1, ct12emptr2, ct12emptr3, ct12dtdig, 
ct12tradu1, ct12ccust1,   ct12tradu2, ct12ccust2, ct12tradu3, 
ct12ccust3, ct12valor, ct12histo1, ct12histo2,   ct12histo3, ct12histo4, 
ct12histo5, ct12histo6, ct12renume, ct12origem  FROM CT12T   WHERE 
ct12emp04 = '500' AND ct12numlot = '20080532' AND ct12numlan = '52' 
FOR UPDATE OF CT12T  for read only;fetch 100 in "SQL_CUR01B5BDE8"

The check box in page 2 is turned off.

Thanks,


Alexandre


Jack Wilson wrote:
> 
> Hiro****,
> 
> I get slightly different error now:
> 
> Error: 42601 ERROR: syntax error at or near "a";
> 
> Here is the sql statement with the trailing semicolon I'm testing 
> with--substitute a valid table name for the word 'my_table' below:
> 
> SELECT  pg_attribute.attname, pg_attribute.attnotnull, 
> pg_attribute.atttypmod, pg_type.typname  
> FROM  pg_attribute  
> JOIN  pg_class ON pg_attribute.attrelid = pg_class.oid  
> JOIN  pg_namespace ON pg_namespace.oid = pg_class.relnamespace  
> JOIN  pg_type on pg_type.oid = pg_attribute.atttypid  
> where  pg_namespace.nspname = 'public'
> AND  pg_class.relname = 'my_table' and  pg_class.relkind = 'r' and 
>  pg_attribute.attnum > 0  
> ORDER BY  pg_attribute.attnum;
> 
> Thanks...jack
> -- 
> ********************************************
> Who:    L Jack Wilson
> Where:  ljwilson@[EMAIL PROTECTED]
> How:    Remove Capital Letters from above for a valid email address
> Why:    Standard Disclaimer fits nicely here.

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc
 




 8 Posts in Topic:
" for read only" clause appended for safety when UseDeclareFetch
ljwilson@[EMAIL PROTECTED  2008-03-05 12:24:27 
Re: " for read only" clause appended for safety when UseDeclareF
inoue@[EMAIL PROTECTED]   2008-03-06 11:24:53 
Re: " for read only" clause appended for safety when UseDeclareF
ljwilson@[EMAIL PROTECTED  2008-03-06 08:14:00 
Re: " for read only" clause appended for safety when UseDeclareF
inoue@[EMAIL PROTECTED]   2008-03-08 03:09:12 
Re: " for read only" clause appended for safety when UseDeclareF
ljwilson@[EMAIL PROTECTED  2008-03-07 14:49:27 
Re: Re: " for read only" clause appended for safety when UseDecl
alepaes@[EMAIL PROTECTED]  2008-06-10 11:45:59 
Re: Re: " for read only" clause appended for safety when UseDecl
alepaes@[EMAIL PROTECTED]  2008-06-10 14:32:01 
Re: Re: " for read only" clause appended for safety when UseDecl
inoue@[EMAIL PROTECTED]   2008-06-11 09:57:08 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Thu Aug 21 22:39:37 CDT 2008.