I have 2 "best practice" questions.
#1 I'm doing lots of:
doMulti.setSqlTextOverrideInsert(CSpSQLObject.FULL_TEXT_OVERRIDE);
and executing various INSERT, UPDATE, DROP commands. I'm wondering if it's smart
to run the Data Object wizard to generate a "dummy" multiSQL DO that simply
selects one column from some table. And then I can reuse this dummy MultiSQL
object whenever I want to issue my FULL_TEXT_OVERRIDE SQL. Otherwise, it seems a
waste to me to bother selecting tables/columns when I know that I'm going to be
specifying them all over again in my code.
I thought maybe the best approach might be: if I happen to have a DO whose SQL
is "close" to the manual SQL I want to execute (i.e. it talks to the same db
table, and maybe I use as a SELECT to initially populate my page) then I should
use it. If not, I should use my "dummy" one.
#2 If I create a MultiSQL DO via the wizard, but know that I'll be executing the
UPDATE via FULL_TEXT_OVERRIDE, should I bother selecting the key columns when
prompted? Or is that only needed when you go the built-in UPDATE route (where ND
will be formulating the WHERE clause using the keys)?
Thanks!
Janet
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
