RE: WARNING:Latest 4GL+Online buggy

Nahh, You are guessing. You assign a select statement to a string. so no error there. You prepare a string at which point spaces are added to the SQL. So what ??. The string assignment would have been okay wouldn't it. ?? I can't see what error you might get during a prepare unless the syntax was incorrect. As it happens the prepare stage also adds spaces in the where clause. eg. Where table1.cola = table2.colb becomes Where table1 . cola = table2 . colb again, so what ?? I've not had any problems with this so far. Mind you I always define my char variables as CHAR(20000). ;-> -----Original Message----- From: Obnoxio The Clown [mailto:obnoxio@hotmail.com] Sent: Tuesday, October 19, 1999 1:02 PM To: richard.spitz@ana.med.uni-muenchen.de; informix-list@iiug.org Subject: Re: WARNING:Latest 4GL+Online buggy From: Richard Spitz <Richard.Spitz@ana.med.uni-muenchen.de> > >David Williams wrote: > > > > The latest 4gl has a bug where preparing a string causes the string > > to have spaces added to it. (Someone here mentioned it, I've logged > > it as a call in the UK.). > > > > e.g. "select a,b,c from t1" becomes > > "select a , b , c from t1" > > after you prepare something from it. > >Why is this a problem? The string with the added spaces is syntactically >identical to the original query and will yield the same result. So why >bother? Or do you do additional things with the string after the >PREPARE? It could be a problem with the length of the string. If you know that the string will never be longer than 20 chars so you define it as a CHAR(20), and suddenly it's 23 chars and this happens before the prepare completes, you might get a syntax error. But I'm just guessing. :-) ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com