Author: ianb
Date: 2006-02-02 15:43:28 -0700 (Thu, 02 Feb 2006)
New Revision: 1559
Modified:
SQLObject/docs/SQLObject.comments.txt
Log:
in page: http://pythonpaste.org/SQLObject.html
by: Big <Man>
Add comment
Modified: SQLObject/docs/SQLObject.comments.txt
===================================================================
--- SQLObject/docs/SQLObject.comments.txt 2006-02-02 22:28:51 UTC (rev 1558)
+++ SQLObject/docs/SQLObject.comments.txt 2006-02-02 22:43:28 UTC (rev 1559)
@@ -24,9 +24,7 @@
ip: 208.255.226.178
username: Mike Kent
-So if you declare a column as an alternateID, unique is implied, and we don't need to explicitly declare it?
-
-shouldn't this be protected???
+So if you declare a column as an alternateID, unique is implied, and we don't need to explicitly declare it?shouldn't this be protected???
==== $(orderby) +
----------------------------------------
date: 2005-12-08T10:47:35
@@ -45,3 +43,12 @@
username: Joe
Think about breaking these SELECT statements onto several lines. They're busting out of the page design now.
+==== $(col-class-specifying-columns) c ++ c +++++ c +
+----------------------------------------
+date: 2006-02-02T15:43:28
+email: Man
+id: 11
+ip: 192.100.104.28
+username: Big
+
+StringCol's that are alternateID's must have a length property if you use them in MySQL.
|