- changed milestone to first release
Shorthand for multiple column comparisons
Issue #13
resolved
When testing for multiple column equivilants, specifying the full class for each column becomes a chore, take this example:
# load a User from the database
sqlmyuser = User.mapper.select(User.c.user_name=='fred', User.c.password=='something',
User.c.email=='someone@somewhere.com')
If we use a slightly different keyword (inspired by SQLObject notation) like so:
# load a User from the database
sqlmyuser = User.mapper.select_by(user_name='fred', password='something', email='someone@somewhere.com')
We save ourselves a bit of repetitive typing. I come across usage like this fairly often so I think it'd be rather useful in SQLAlchemy as well.
Comments (3)
-
repo owner -
repo owner - changed status to resolved
fixed in changeset:710. Will also look into relationships for the keynames if not found in the local set of property and column names, and generate the appropriate joins.
-
repo owner - removed milestone
Removing milestone: 0.2.0 (automated comment)
- Log in to comment