[SQL-CVS] r659 - trunk/SQLObject/docs

[<sub...@co...>]

Author: phd
Date: 2005-03-01 14:52:06 +0000 (Tue, 01 Mar 2005)
New Revision: 659

Modified:
   trunk/SQLObject/docs/FAQ.txt
   trunk/SQLObject/docs/SQLObjectCustomization.txt
   trunk/SQLObject/docs/SQLObjectLegacy.txt
   trunk/SQLObject/docs/SQLObjectUse.txt
Log:
Fixed https://sourceforge.net/tracker/index.php?func=detail&aid=1072399&group_id=74338&atid=540672 -
all mentions of .new() replaced with constructors.


Modified: trunk/SQLObject/docs/FAQ.txt
===================================================================
--- trunk/SQLObject/docs/FAQ.txt	2005-03-01 14:22:14 UTC (rev 658)
+++ trunk/SQLObject/docs/FAQ.txt	2005-03-01 14:52:06 UTC (rev 659)
@@ -159,7 +159,7 @@
 ``CREATE TABLE`` generation (i.e., ``createTable``).  You also will
 have to give your own ID values when creating an object, like::
 
-    color = Something.new(id="blue", r=0, b=100, g=0)
+    color = Something(id="blue", r=0, b=100, g=0)
 
 IDs are, and always will in future versions, be considered immutable.
 Right now that is not enforced; you can assign to the ``id``

Modified: trunk/SQLObject/docs/SQLObjectCustomization.txt
===================================================================
--- trunk/SQLObject/docs/SQLObjectCustomization.txt	2005-03-01 14:22:14 UTC (rev 658)
+++ trunk/SQLObject/docs/SQLObjectCustomization.txt	2005-03-01 14:52:06 UTC (rev 659)
@@ -41,8 +41,8 @@
 keep in files as opposed to the database (such as large, opaque data
 like images).
 
-You can also pass an ``image`` keyword argument to the `new` class
-method or the `set` method, like ``Person.new(..., image=imageText)``.
+You can also pass an ``image`` keyword argument to the constructor
+or the `set` method, like ``Person(..., image=imageText)``.
 
 All of the methods (``_get_``, ``_set_``, etc) are optional -- you can
 use any one of them without using the others (except ``_doc_``, since

Modified: trunk/SQLObject/docs/SQLObjectLegacy.txt
===================================================================
--- trunk/SQLObject/docs/SQLObjectLegacy.txt	2005-03-01 14:22:14 UTC (rev 658)
+++ trunk/SQLObject/docs/SQLObjectLegacy.txt	2005-03-01 14:52:06 UTC (rev 659)
@@ -93,4 +93,4 @@
 category of "irregularities".  If you use non-integer keys, all
 primary key management is up to you.  You must create the table
 yourself, and when you create instances you must pass a ``id`` keyword
-argument into ``new`` (like ``Person.new(id='555-55-5555', ...)``).
+argument into constructor (like ``Person(id='555-55-5555', ...)``).

Modified: trunk/SQLObject/docs/SQLObjectUse.txt
===================================================================
--- trunk/SQLObject/docs/SQLObjectUse.txt	2005-03-01 14:22:14 UTC (rev 658)
+++ trunk/SQLObject/docs/SQLObjectUse.txt	2005-03-01 14:52:06 UTC (rev 659)
@@ -16,7 +16,7 @@
    method fetches a row.
 
 To create a new object (and row), use class instantiation.  In this
-case you might call ``Person.new(firstName="John", lastName="Doe")``.
+case you might call ``Person(firstName="John", lastName="Doe")``.
 If you had left out ``firstName`` or ``lastName`` you would have
 gotten an error, as no default was given for these columns
 (``middleInitial`` has a default, so it will be set to ``NULL``, the