Re: Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons

[alepaes - aldeia digital <alepaes(at)aldeiadigital(dot)com(dot)br>]

Sorry,

I mean: "PGODBC 8.03.0200 have the same problem"


alepaes - aldeia digital wrote:
> 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, ct12docume, 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:
> > Hiroshi,
> >
> > 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(at)dNiOgSiPtAaMlav(dot)com
> > How:    Remove Capital Letters from above for a valid email address
> > Why:    Standard Disclaimer fits nicely here.