Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Michel Pelletier
committed
Jul 3, 2000
1 parent
25b5554
commit 19f35a4
Showing
1 changed file
with
144 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,144 @@ | ||
############################################################################## | ||
# | ||
# Zope Public License (ZPL) Version 1.0 | ||
# ------------------------------------- | ||
# | ||
# Copyright (c) Digital Creations. All rights reserved. | ||
# | ||
# This license has been certified as Open Source(tm). | ||
# | ||
# Redistribution and use in source and binary forms, with or without | ||
# modification, are permitted provided that the following conditions are | ||
# met: | ||
# | ||
# 1. Redistributions in source code must retain the above copyright | ||
# notice, this list of conditions, and the following disclaimer. | ||
# | ||
# 2. Redistributions in binary form must reproduce the above copyright | ||
# notice, this list of conditions, and the following disclaimer in | ||
# the documentation and/or other materials provided with the | ||
# distribution. | ||
# | ||
# 3. Digital Creations requests that attribution be given to Zope | ||
# in any manner possible. Zope includes a "Powered by Zope" | ||
# button that is installed by default. While it is not a license | ||
# violation to remove this button, it is requested that the | ||
# attribution remain. A significant investment has been put | ||
# into Zope, and this effort will continue if the Zope community | ||
# continues to grow. This is one way to assure that growth. | ||
# | ||
# 4. All advertising materials and documentation mentioning | ||
# features derived from or use of this software must display | ||
# the following acknowledgement: | ||
# | ||
# "This product includes software developed by Digital Creations | ||
# for use in the Z Object Publishing Environment | ||
# (http://www.zope.org/)." | ||
# | ||
# In the event that the product being advertised includes an | ||
# intact Zope distribution (with copyright and license included) | ||
# then this clause is waived. | ||
# | ||
# 5. Names associated with Zope or Digital Creations must not be used to | ||
# endorse or promote products derived from this software without | ||
# prior written permission from Digital Creations. | ||
# | ||
# 6. Modified redistributions of any form whatsoever must retain | ||
# the following acknowledgment: | ||
# | ||
# "This product includes software developed by Digital Creations | ||
# for use in the Z Object Publishing Environment | ||
# (http://www.zope.org/)." | ||
# | ||
# Intact (re-)distributions of any official Zope release do not | ||
# require an external acknowledgement. | ||
# | ||
# 7. Modifications are encouraged but must be packaged separately as | ||
# patches to official Zope releases. Distributions that do not | ||
# clearly separate the patches from the original work must be clearly | ||
# labeled as unofficial distributions. Modifications which do not | ||
# carry the name Zope may be packaged in any form, as long as they | ||
# conform to all of the clauses above. | ||
# | ||
# | ||
# Disclaimer | ||
# | ||
# THIS SOFTWARE IS PROVIDED BY DIGITAL CREATIONS ``AS IS'' AND ANY | ||
# EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE | ||
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR | ||
# PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL DIGITAL CREATIONS OR ITS | ||
# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, | ||
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT | ||
# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF | ||
# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND | ||
# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, | ||
# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT | ||
# OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | ||
# SUCH DAMAGE. | ||
# | ||
# | ||
# This software consists of contributions made by Digital Creations and | ||
# many individuals on behalf of Digital Creations. Specific | ||
# attributions are listed in the accompanying credits file. | ||
# | ||
############################################################################## | ||
|
||
|
||
class ZSQLMethod: | ||
""" | ||
ZSQLMethods abstract SQL code in Zope. | ||
They support three important abstractions: | ||
- Method | ||
SQL Methods behave like methods of the folders they are | ||
accessed in. In particular, they can be used from other | ||
methods, like Documents, ExternalMethods, and even other SQL | ||
Methods. | ||
- Searchability | ||
Database methods support the Searchable Object Interface. | ||
Search interface wizards can be used to build user | ||
interfaces to them. They can be used in joins and | ||
unions. They provide meta-data about their input parameters | ||
and result data. | ||
For more information, see the searchable-object interface | ||
specification. | ||
- Containment | ||
Database methods support URL traversal to access and invoke | ||
methods on individual record objects. For example, suppose you | ||
had an 'employees' database method that took a single argument | ||
'employee_id'. Suppose that employees had a 'service_record' | ||
method (defined in a record class or acquired from a | ||
folder). The 'service_record' method could be accessed with a | ||
URL like:: | ||
employees/employee_id/1234/service_record | ||
""" | ||
|
||
|
||
def __call__(self, REQUEST=None, **kw): | ||
""" | ||
Call the ZSQLMethod. | ||
The arguments to the method should be passed via keyword | ||
arguments, or in a single mapping object. If no arguments are | ||
given, and if the method was invoked through the Web, then the | ||
method will try to acquire and use the Web REQUEST object as | ||
the argument mapping. | ||
The returned value is a sequence of record objects. | ||
XXX describe record objects XXX | ||
""" | ||
|
||
|