Subject | RE: [IBO] IB_Query phenomenom |
---|---|
Author | John Tomaselli |
Post date | 2001-01-03T04:57:34Z |
Jason,
I'm a little confused by your suggestion. I build all by complex queries
with join logic then use the onPrepareSql to provide the various user
selections made on a form using the sqlwhereitems method. i.e.
sqlwhereitems.add('X.fieldname = '+form_edit.text). If all this was moved to
the join part of the query wouldn't you loose all this great functionality.
John
-----Original Message-----
From: Jason Wharton [mailto:jwharton@...]
Sent: Tuesday, January 02, 2001 10:29 PM
To: IBObjects@egroups.com
Subject: Re: [IBO] IB_Query phenomenom
JOIN area.
Remember the rule of thumb. DON'T put anything in the WHERE clause that is a
part of the JOIN.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
I'm a little confused by your suggestion. I build all by complex queries
with join logic then use the onPrepareSql to provide the various user
selections made on a form using the sqlwhereitems method. i.e.
sqlwhereitems.add('X.fieldname = '+form_edit.text). If all this was moved to
the join part of the query wouldn't you loose all this great functionality.
John
-----Original Message-----
From: Jason Wharton [mailto:jwharton@...]
Sent: Tuesday, January 02, 2001 10:29 PM
To: IBObjects@egroups.com
Subject: Re: [IBO] IB_Query phenomenom
> where A.FMMPID=11 and B.FMMPID=12 and C.FMMPID=13I think the stuff in the WHERE clause should be brought up into the FROM ...
JOIN area.
Remember the rule of thumb. DON'T put anything in the WHERE clause that is a
part of the JOIN.
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com