-Original Message-
From: Bill Downall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 09, 2004 10:38 AM
To: [EMAIL PROTECTED]
Subject: RE: Witango-Talk: DBMS Action Select with Limit # or Rows
A followup:
This definitely was broken in Witango server 5.0 after patch .58 and
before
patch .65. I
What do I do to trace these at the level that would be useful? It's
obviously not just the SQL in the Witango debugging output.
When I go into ODBC Administrator and Start Tracing now using the default
odbctrac.dll, and then hit the Oterro database driver through the Witango
application,
Message-
From: Bill Downall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 10, 2004 9:24 AM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: DBMS Action Select with Limit # or Rows
What do I do to trace these at the level that would be useful? It's
obviously not just the SQL in the Witango
At 10:16 AM 3/10/2004, you wrote:
Bill Oterro doesn't log to the ODBC Log.
You need to do this:
Add the line:
DEBUG ON
to the Oterro.cfg file.
This will create an Oterro.log file in the C:\ directory
Ben Johansen - http://www.pcforge.com
Authorized Witango MDaemon Reseller
Available for Witango
-Original Message-
From: Bill Downall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 10, 2004 2:21 PM
To: [EMAIL PROTECTED]
Subject: RE: Witango-Talk: DBMS Action Select with Limit # or Rows
Ben,
Actually, it turns out
At 03:46 PM 3/10/2004, you wrote:
There has been a change, if I recall correctly.
Oterro 3.0 is RDEBUG ON.
Chuck Lockwood
Chuck
DEBUG ON worked for me with 3.0. I think the change was the name and
location of the log, from Microrim.log to c:\Oterro.log, as of Oterro
version 2.6.
Bill
Steve,
Are you using the builders?
These work fine for me with Oterro 2.6 and 3.0, with the limit to xx rows
and previous xx and next xx links, but I have customized the builder
considerably.
Bill
At 11:12 PM 3/8/2004, you wrote:
I am trying to construct a DBMS Select action that will limit
: Re: Witango-Talk: DBMS Action Select with Limit # or Rows
Steve,
Are you using the builders?
These work fine for me with Oterro 2.6 and 3.0, with the limit to xx rows
and previous xx and next xx links, but I have customized the builder
considerably.
Bill
At 11:12 PM 3/8/2004, you wrote:
I am
Steve,
The limit does the following.
It processes the full select and then limits the rows returning.
So if the select returns a 100 rows with the limit, then the limit = 20
prevents the last 80 from returning.
Your are better servered by using the COUNT criteria
Ben Johansen -
Steve,
This is quite weird! I went to look at my taf that does this just fine, and
it doesn't do this just fine anymore!
I have a taf that pages in 50s, and has been working great this way with
next/previous buttons and your configuration as below, except that at the
client site is is Oterro
A followup:
This definitely was broken in Witango server 5.0 after patch .58 and before
patch .65. I have a site still running on .58. A taf that observes the
limit and pages groups of 40 just fine in .58 puts the whole result set on
the page on a server running .65.
I'll send the example
Thanks Bill. I thought something was up here.
Steve
-Original Message-
From: Bill Downall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 09, 2004 10:38 AM
To: [EMAIL PROTECTED]
Subject: RE: Witango-Talk: DBMS Action Select with Limit # or Rows
A followup:
This definitely was broken
Steve,
You are probably better doing this with a custom SQL action. What SQL server are you using?
J.
On 09/03/2004, at 3:12 PM, Fogelson, Steve wrote:
I am trying to construct a DBMS Select action that will limit the number of
rows retrieved.
x-tad-bigger
/x-tad-biggerx-tad-biggerWITH
Ted,
There is not a performance hit, unless you don't have an index on the
column that generates the list. Your best bet, since you are using a direct
DBMS action, is a sub-query:
SELECT a, bunch, of, columnnames
FROM maintable
WHERE columnvalue IN (SELECT othertablecolumn FROM
columnvalue IN (SELECT othertablecolumn FROM othertable
WHERE somecolumn = '@VAR request$varname' )
and now all is well!
- Original Message -
From: Bill Downall [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 08, 2003 11:56 AM
Subject: Re: Witango-Talk: DBMS action
Ted
Message-
From: Atrix Wolfe [mailto:[EMAIL PROTECTED]
Sent: Monday, September 08, 2003 3:15 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: DBMS action
we at one point used alot of this:
SELECT a, bunch, of, columnnames
FROM maintable
WHERE columnvalue IN (@ARRAY request$valuelist
On Mon, 8 Sep 2003 15:26:31 -0400, Ted Wolfley wrote:
Just a side note, I did not use the 0 with my array variable and I still
retrieved all the data. Is this a glitch or just safe coding?
Ted,
It may have been a recent clever enhancement to Oterro to let us get away
with that. I know when I
Not Really,
all the search action does is make it simpler to create SQL Statements. The
SQL statement is stored within the XML. So the server just processes the SQL
statement.
Ben Johansen - http://www.pcforge.com
-Authorized WiTango Reseller
http://www.pcforge.com/WitangoGoodies.htm
-Talk: DBMS action
Not Really,
all the search action does is make it simpler to create SQL Statements. The
SQL statement is stored within the XML. So the server just processes the SQL
statement.
Ben Johansen - http://www.pcforge.com
-Authorized WiTango Reseller
http://www.pcforge.com
Steve - why do you need to do this? Is the null field causing a
problem, or is it something else? Would it help any to change the WHERE
clause to AND ((o5.OV_ID = b2.OV_ID3) OR b2.OV_ID3 IS NULL) , so that
the clause was true if either the two IDs match or the ID3 value is
null?
You
Steve,
You can build your complete SQL in variables in a results action,
modifying the SELECT list, the FROM list, and the WHERE conditions
according to some IF conditions. Of course, you will have to SELECT
the ov_id3 column from the appropriate BASKET row first, to set up
your if
.
Steve Fogelson
-Original Message-
From: Bill Downall [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 18, 2003 12:41 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: DBMS Action
Steve,
You can build your complete SQL in variables in a results action,
modifying the SELECT list
On Tue, 18 Feb 2003 13:24:22 -0600, Fogelson, Steve wrote:
I guess I was wondering how the Incl. Empty option in the criteria
of a
search action could be related to a DBMS. I understand this option
(if set
to false) to not include a criteria if null.
No, those settings deal with data that
At 01:46 PM 2/18/2003, you wrote:
On Tue, 18 Feb 2003 13:24:22 -0600, Fogelson, Steve wrote:
I guess I was wondering how the Incl. Empty option in the criteria
of a
search action could be related to a DBMS. I understand this option
(if set
to false) to not include a criteria if null.
No, those
On Tue, 18 Feb 2003 15:25:44 -0600, Eric Weidl wrote:
That is incorrect.
Eric,
Maybe I didn't explain clearly enough, but it was definitely not incorrect
g.
Steve's got a handle on what you are talking about. He would like to be
able to not include if empty a JOIN condition between tables.
25 matches
Mail list logo
