Well there are two methods to make a SQL statement: 1. Have all the statements hard coded as you mentioned 2. Pass the script in hyperlink form mode to another page which actually executed the statement: [Page 1 - The gathering page] [Page 2 - the parsing page] <META HTTP-EQUIV="Refresh" Content="0; URL= www.me.com/page3.stm?sql=SELECT <RCif RC$var1 ! NULL AND RC$var1 = this> field1, <RC$endif> <RCif RC$var# ! NULL AND RC$var# = that> field2, <RCendif> from <RC$table> where <RCif RC$var1 ! NULL AND RC$var1 = this> tag1 = <RC$var1> <RCendif> <RCif RC$var1 ! NULL AND RC$var# ! NULL> AND <RCendif> <RCif RC$var1 ! NULL AND RC$var1 < this> tag2 LIKE <RC$var#> > [Page 3 - the executing page]
Very simple example - I'm sure you get the idea. I could give a big complicated sucker but it's very confusing. We would be able to use the <RCinclude> to call the 3 pages to: <RCinclude /page3.stm?sql=... > However as you can see this is very messy. Matt. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Ray Noel Sent: September 12, 2002 5:33 AM To: [EMAIL PROTECTED] Subject: [sambar] Database scripting. {06} Thanks for the input Matt. Any chance of a copy of a script as you outlined please. It would be useful.. The other scenario I want to be able to code is user-selected fields..... Cheers Ray At 05:33 PM 12/09/2002, you wrote: >And yes it would be nice if I could build a dynamic template without >passing to or calling another page with a meta tag >(page2.stm?sql=<RCif>.....<RCendif>). > >It is 4am - I am going to bed :) > >Matt. >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf >Of M. Skeoch (CDS) >Sent: September 12, 2002 4:27 AM >To: [EMAIL PROTECTED] >Subject: [sambar] Database scripting. {04} > >Ahhhhhh... I see. > >In the past I have built each call statement then bound it to a RC$tag. >Depending on what you want, it calls the appropriate one for the RCQ. >However, you are right, this requires multiple IF statements - but only >for each template. > >Matt. > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf >Of Ray Noel >Sent: September 12, 2002 3:32 AM >To: [EMAIL PROTECTED] >Subject: [sambar] Database scripting. {03} > >Yes Matt, > >Shot myself in the foot here. Bad example, I can't understand it either >:-) > >But suppose the user wanted one of four or five types of reports which >could be ordered on 4 or 5 different fields. >What I would like to be able to do is examine each variable separately >and >create the SQL string dynamically, then pass the SQL string to the >query. >For example, queries on an asset register might be for many purposes, >annual stocktake, warranty period expiry, manufacturers recall, etc. >Each of the above reports might require different fields and might be >ordered differently, which is easily catered for if you can build the >SQL >string to suit each purpose without the necessity for multiple nested ><RCif>'s. > >Hopefully that is nearer what I was trying to say earlier... > >Regards >Ray > > >At 04:03 PM 12/09/2002, you wrote: > > >#Hello to all list members, > > > >#I guess this database scripting question is really for Tod, but maybe > >it's > >#already easily achievable with the existing Sambar database scripting. > >#How can I code a query based on as many as six user-selected options > >#without a complex nested <RCif> structure and multiple hard-coded SQL > >#statements? > > > >Are you looking to drop or add any of the statements if the statement >is > >empty or not selected? > > > >#I think this sort of thing is referred to as Query-by-Example. It's > >easily > >#achievable using other scripting languages like PHP, where the query > >string > >#is built incrementally and executed once and I'm hoping it might be a > >#simple programming operation for Tod to give Sambar scripters the > >option of > >#either hard-coding the string or using a <RC$sqlstring> variable that > >can > >#be created incrementally, based on contents of other <RC$> variables > >passed > >#to the .stm script. > > > >#An example > >#<RC$sqlstatement = "select workstationid, supplier, serialnumber, ram, > >hdd > > from machine > > where location = 'RC$location' and >supplier > >= > >#'RC$supplier' and ram = 'RC$ram' and hdd = 'RC$hdd'"> > > > >#<RCQtest sql="$RC$sqlstatement" > > format="<TR><TD>%s<TD>%s</TD><TD>%s</TD><TR>" > > > > >This example works (with the exception of the front $ on > >$RC$sqlsatement) - is this a current or future example? > > > >#The above query was difficult to code and maintain > > > >Why is the above example difficult to maintain and code? > > > >#and I do believe the suggested additional query method would > >#**significantly enhance** Sambar Server functionality. What do you > >think #list members, Tod? > > > >I guess I don't understand what you mean :( > > > >I've been using Sambar query to do everything including very complex >and > >long procedures without running into any problems. > > > >Matt. > >------------------------------------------------------- > >To unsubscribe please go to http://www.sambar.ch/list/ >------------------------------------------------------- >To unsubscribe please go to http://www.sambar.ch/list/ >------------------------------------------------------- >To unsubscribe please go to http://www.sambar.ch/list/ >------------------------------------------------------- >To unsubscribe please go to http://www.sambar.ch/list/ ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/ ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
