Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Changes between Version 7 and Version 8 of UsingSqlAlchemy


Ignore:
Timestamp:
02/15/06 16:51:52 (9 years ago)
Author:
KarlGuertin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UsingSqlAlchemy

    v7 v8  
    1616Notable advantages of SQLAlchemy over SQLObject are the ability to map 
    1717arbitrary selects, the ability to map muliple tables/selects onto a single 
    18 object, and support for composite primary keys.  SQLAlchemy object properties 
    19 by default retain their database-like lowercase_with_underscores names used 
    20 standardly in Python instead of SQLObject's mixedCase names. 
     18object, and support for composite primary keys. 
    2119 
    2220The disadvantage is that SQLAlchemy is more complex than SQLObject, requiring 
    2321separate table description, object declaration, and object mapping statements. 
     22SQLAlchemy object properties retain their database name, while SQLObject provides 
     23the styles package to allow name reformatting to suit your taste. 
    2424 
    2525If you use SQLAlchemy, you will lose access to fastdata. This could be fixed 
    2626rather simply by adding sqlalchemy-knowledgable conditions to the RuleDispatch 
    27 checks in ``formmaker.py``. There are no other disadvantages to using 
    28 SQLAlchemy with TurboGears. 
     27checks in ``formmaker.py``. You will also lose the use of CatWalk/ModelDesigner 
     28and will have to explicitly call ``objectstore.commit()`` in your controller 
     29(i.e. transactions are not implicit). 
    2930 
    3031This document covers the 0.1.0 release and was written on February 13, 2006.