Subject | Re: Quoted Fields |
---|---|
Author | Rohit Gupta |
Post date | 2001-01-12T02:11:53Z |
As mentioned in the original post, we are using th ibDataset and are
nopt generating any SQL statements, the app being a port from btrieve
to IBX (which was too slwo) to now IBO. Hence, there is no ambiguity
involved - the IBO component knows which are field names and which
are not. Not only are the Fieldname sin FieldDefs, it also inserts
the fieldnames into the SQL statements, not me.
Furthermore the quotes are not part of the name, they are a way to
allow names that we want to be given to the tablenames and fieldnames.
nopt generating any SQL statements, the app being a port from btrieve
to IBX (which was too slwo) to now IBO. Hence, there is no ambiguity
involved - the IBO component knows which are field names and which
are not. Not only are the Fieldname sin FieldDefs, it also inserts
the fieldnames into the SQL statements, not me.
Furthermore the quotes are not part of the name, they are a way to
allow names that we want to be given to the tablenames and fieldnames.
--- In IBObjects@egroups.com, "Jason Wharton" <jwharton@i...> wrote:
> > We feel that the quotes should be added and stripped by the
ibocomponents
> > when using dialect 3, automatically.
>
> I would gladly do that if it wasn't forcing me to make assumptions
where
> ambiguity is involved.
>
> IBX has done you a grave disservice by allowing such to take place.
>
> One thing I might suggest is to see if GExperts can lend a hand by
going
> through and making some substitutions automatically for you.
>
> Another things I might consider if things are serious enough, is to
allow a
> session level property that tells IBO to make assumptions as IBX
does about
> things. I'd sure rather not have to carry the weight of their poor
design
> decisions though.
>
> You realize what you are asking for is something like this:
>
> Make the IB SQL parsing routines smart enough to discern this
statement:
>
> SELECT * FROM MyBigTable
>
> as if it were this statement:
>
> SELECT * FROM "MyBigTable"
>
> If an identifier is asked for, you've got to spell it all right or
it isn't
> going to work. IBX is down right sloppy for making assumptions where
> ambiguity is present. These two statements are not equivalent and
one or the
> other will produce an error to the IB parser. Unless there are two
tables
> named accordingly, which could lead to an even bigger problem.
>
> My recommendation is to take your lumps and get out of IBX before
it bites
> you somewhere else too.
>
> FWIW,
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: "Rohit Gupta" <r.gupta@x...>
> To: <IBObjects@egroups.com>
> Sent: Thursday, January 11, 2001 4:44 PM
> Subject: [IBO] Quoted Fields
>
>
> > We are in the process of evaluating IBO by shifting from IBX to
IBO
> because
> > IBX is just too slow.
> >
> > We are using Dialect 3 with quoted fields to be able to use
reserved names
> > such as Number and Type. And we are using quoted indexnames to
preserve
> > the case because it is far more readable by our clients that way.
> >
> > We are using ionly the components under the iboTDataset Tab as we
are
> moving
> > from Btrieve to Interbase and have to preserve the 200+ forms.
> >
> > Whereas IBX stripped and inserted quotes as necessary, there
doesnt appear
> > to be a theme in IBO. The probelm we have is that to get thinsg
working
> it
> > appears that we have to go through all the forms and add quotes
around
> each
> > persistent field and each indexname in each component - table,
navigator,
> > grid etc.
> >
> > Also, we have to chage all tablenames in many components on all
forms
> >
> > Are there any properties to help with this ? Any other ideas ?
going thru
> > that many forms is a mamoth job.
> >
> > We feel that the quotes should be added and stripped by the
ibocomponents
> > when using dialect 3, automatically.