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 6 and Version 7 of UsingSqlAlchemy


Ignore:
Timestamp:
02/14/06 23:13:08 (13 years ago)
Author:
mgood
Comment:

SQLAlchemy's property names are not a disadvantage, it's SQLObject's mixedCase names that differ from the standard modules and  PEP 8

Legend:

Unmodified
Added
Removed
Modified
  • UsingSqlAlchemy

    v6 v7  
    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. 
     18object, and support for composite primary keys.  SQLAlchemy object properties 
     19by default retain their database-like lowercase_with_underscores names used 
     20standardly in Python instead of SQLObject's mixedCase names. 
    1921 
    2022The disadvantage is that SQLAlchemy is more complex than SQLObject, requiring 
    2123separate table description, object declaration, and object mapping statements. 
    22 SQLAlchemy objects by default retain their database_names rather than 
    23 SQLObject's pythonicNames. 
    2424 
    2525If you use SQLAlchemy, you will lose access to fastdata. This could be fixed