[SQL-CVS] SQLObject/docs News.txt,1.4,1.5
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
|
From: <ian...@us...> - 2003-04-07 20:11:32
|
Update of /cvsroot/sqlobject/SQLObject/docs
In directory sc8-pr-cvs1:/tmp/cvs-serv17865
Modified Files:
News.txt
Log Message:
Updated
Index: News.txt
===================================================================
RCS file: /cvsroot/sqlobject/SQLObject/docs/News.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** News.txt 14 Mar 2003 09:10:11 -0000 1.4
--- News.txt 7 Apr 2003 20:11:28 -0000 1.5
***************
*** 14,21 ****
--------
* New column classes (see `Col` module), indicates type
! * Table creation (SQL schema generation) via new class method
! `createTable`.
* Objects are not cached indefinitely. Cached objects are expired
--- 14,28 ----
--------
+ * Table creation (SQL schema generation) via new class method
+ `createTable`. And of course a `dropTable` method to go with.
+
+ * Add and remove columns at runtime, optionally modifying the
+ schema in the database (via ``ALTER``). (Does not work in
+ SQLite)
+
* New column classes (see `Col` module), indicates type
! * Classes can be created by parsing an already existant table
! (MySQL only).
* Objects are not cached indefinitely. Cached objects are expired
***************
*** 25,28 ****
--- 32,57 ----
pass ``nocache=True`` to your connection object to eliminate as much
caching as possible. See `Cache` module for a bit more.
+
+ * New DBMConnection, implements a database-like backend without any
+ database to speak of, including queries (so long as you use
+ `SQLBuilder` and don't generate your where clauses manually).
+ Actual SQL generation is done entirely by the database connection,
+ allowing portability across very different backends.
+
+ * Postgres table IDs should be created with type ``SERIAL`` (which
+ implicitly creates a sequence).
+
+ * New `_defaultOrder` class variable gives a default for the
+ `orderBy` parameter to `select` queries.
+
+ Bugs
+ ----
+
+ * LIMIT/OFFSET (select result slicing) works in Postgres and SQLite.
+
+ * ``tableExists`` method from DBConnection works in same.
+
+ * mxDateTime not required (never should have been, always just an
+ option).
SQLObject 0.2.1
|