Thread: [SQL-CVS] r175 - trunk/SQLObject/docs
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: <sub...@co...> - 2004-08-18 00:44:32
|
Author: ianb Date: 2004-08-17 16:35:43 -0400 (Tue, 17 Aug 2004) New Revision: 175 Modified: trunk/SQLObject/docs/News.txt Log: Note cascade keyword argument addition Modified: trunk/SQLObject/docs/News.txt =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/SQLObject/docs/News.txt 2004-08-17 20:31:15 UTC (rev 174) +++ trunk/SQLObject/docs/News.txt 2004-08-17 20:35:43 UTC (rev 175) @@ -37,9 +37,17 @@ * We're now using a Subversion repository instead of CVS. It is located at svn://colorstudy.com/trunk/SQLObject=20 =20 -* If you pass ``forceDBName=3DTrue`` to the `*Col` constructors, then +* If you pass ``forceDBName=3DTrue`` to the ``*Col`` constructors, then your column name doesn't have to be restricted to a-z, 0-9, and _. =20 +* ``*Col`` constructors now support cascade: ``cascade=3DNone`` + (default) means no constraint; ``cascade=3DTrue`` means that if the + foreign key is deleted, the object will be deleted; + ``cascade=3DFalse`` means that the delete will fail. ``SET NULL`` is + not implemented, and the constraints are only implemented in the + DBMS, not in SQLObject (i.e., they will not work in databases like + MySQL and SQLite). + Bugs ---- =20 |