Re: [Zope-dev] Z SQL: "optional" isn't?
Kyler B. Laird writes:
I'd like to build a Z SQL method for *many* people to use to list courses that we offer. I don't want to require that all queries using it understand all of the columns, but I do want to be able to modify the query in many ways.
This works only if I provide at least an empty string for all values. If I don't provide a value at all for one of the arguments, I get Error, Bad Request: ['version'] You want to use "default values" in your SQL method argument list.
The details are described in "ZSQL/ZSQL.2.5.2.html". You already got this advice. You failed, because you used the wrong kind of quotes (i.e. single rather than double quotes). Quote from "ZSQL2.5.2.html":
See Database method input argument format: Argument name and type are separated by a colon. A equal sign separates the default value from the name and type. The default value is a string representation of the desired value. If the default value contains spaces, or is an empty string, then it must be surrounded by double quotes.)
Pattern: name:type="default"
Dieter
On Mon, 29 May 2000 21:56:33 +0200 (CEST) you wrote:
Error, Bad Request: ['version'] You want to use "default values" in your SQL method argument list.
The details are described in "ZSQL/ZSQL.2.5.2.html".
What's the URL for this? I'm looking through the pointers from the documentation page and only finding http://www.zope.org/Documentation/Guides/ZSQL-HTML/ZSQL.1.5.2.html I even tried a search and only came up with ZSQL 1.* hits.
Quote from "ZSQL2.5.2.html":
See Database method input argument format: Argument name and type are separated by a colon. A equal sign separates the default value from the name and type. The default value is a string representation of the desired value. If the default value contains spaces, or is an empty string, then it must be surrounded by double quotes.)
This is not the same functionality as is provided by the "optional" attribute. How would I use it with an integer, for example? I don't want a default value; I want the option of not having the value set at all. I like the optional attribute. I'd like to see it do more than sit idle in the code. --kyler
On Mon, 29 May 2000, Kyler B. Laird wrote:
This is not the same functionality as is provided by the "optional" attribute. How would I use it with an integer, for example? I don't want a default value; I want the option of not having the value set at all.
I like the optional attribute. I'd like to see it do more than sit idle in the code.
You don't have to do the typechecking in the 'arguments' box if you don't want. eg. in your arguments section: course="" subject="" And your method: select * from enrolments <dtml-sqlgroup where> <dtml-sqltest course type=int optional> <dtml-sqltest subject type=nb optional> </dtml-sqlgroup> The definition of the 'optional' tag from the docs might help here: '''A flag indicating if the test is optional. If the test is optional and no value is provided for a variable, or the value provided is an invalid empty string, then no text is inserted''' Hmm... looking at this definition, it seems you have found a bug (but setting the default value to "" in the arguments section will provide a workaround). Or maybe 'no value provided' means 'is None'. Anyone from DC want to provide a ruling? :-) -- Stuart Bishop Work: zen@cs.rmit.edu.au Senior Systems Alchemist Play: zen@shangri-la.dropbear.id.au Computer Science, RMIT University
On Tue, 30 May 2000 17:09:20 +1000 (EST) you wrote:
I like the optional attribute. I'd like to see it do more than sit idle in the code.
You don't have to do the typechecking in the 'arguments' box if you don't want. eg. in your arguments section:
course="" subject=""
O.k., it appears that I can still use that with integers. I can live with that. I don't like setting an integer to what appears to be a string, but it does work.
select * from enrolments <dtml-sqlgroup where> <dtml-sqltest course type=int optional> <dtml-sqltest subject type=nb optional> </dtml-sqlgroup>
The definition of the 'optional' tag from the docs might help here: '''A flag indicating if the test is optional. If the test is optional and no value is provided for a variable, or the value provided is an invalid empty string, then no text is inserted'''
I should have been more specific. I was referring to the "optional" attribute of the *argument* (not the sqltest). I found that it's coded in Aqueduct.py, but I'm not aware of any way to set it from the Z SQL method form.
Hmm... looking at this definition, it seems you have found a bug (but setting the default value to "" in the arguments section will provide a workaround). Or maybe 'no value provided' means 'is None'. Anyone from DC want to provide a ruling? :-)
Originally, after reading the above ("optional" in sqltest) definition, I'd hoped to be able to simply list the variable in the arguments section and make it optional in the sqltest. After looking at the code, I determined that this was not a reasonable expectation. (What if I used two sqltests and it was only optional in one?) In the course of investigating this, however, I found that an optional attribute for an argument is recognized. It seems like this is what should be used. I can live with it either way, but I think that optional is better than integer_var="". I'd like to see whatever is chosen documented, and I'd like to see "optional" removed from Aqueduct.py if it's not going to be supported. (Maybe it's used by something else?) --kyler
participants (3)
-
Dieter Maurer -
Kyler B. Laird -
Stuart 'Zen' Bishop