Thanks for the great release :)
On 7 sep., 19:40, Michael Bayer mike...@zzzcomputing.com wrote:
SQLAlchemy 0.6.4 is now available, with a significantly large number of
enhancements and fixes.
A large focus of this release is on clarification and ease of use, including:
- the largest
Hi All,
I'm trying to solve a hierarchical access control problem, both on the
storage and querying side.
So, say I have a tree of content:
/
/a/
/a/1
/a/2
/b/
/b/1
/b/2
I want to be able to express and search on the following types of
requirements:
User X should be able to access all
Hi everyone, I'm getting in troubles doing some experiments with
sqlalchemy (0.6.3) orm. Here are two code snippets to show the
problems I'm encountering.
## map_1.py
engine = create_engine(mysql://user:passw...@localhost/mydb)
metadata = MetaData(engine)
parent_table = Table('parent', metadata,
When I try to use both aliases and labels, the results are not named
as expected.
Instead of being able to access the columns as label-name_column-
name it appears as original-table-name_numeric-sequence_column-
name
Thanks,
Jack
Sample code follows:
parent = Table('parent', metadata,
Hi Chris,
this is more of a relational design question than SQLAlchemy-related,
but take a look at this for an at-a-glance summary of different
approaches and their pros and cons:
http://vadimtropashko.wordpress.com/2008/08/09/one-more-nested-intervals-vs-adjacency-list-comparison/
... here for
That is for comparing *Clauses* and handles:
locations.siteid = :param_1
and
:param_1 = locations.siteid
However,
locations.siteid = :param_1 AND locations.locationid = :param_2
and
locations.locationid = :param_1 AND locations.siteid = :param_2
are ClauseLists, which compares their individual
I've got a recipe for what will work well for us. I imagine it could
be useful for others, although I left out the actual serialization
mechanism, since that will likely be very project specific.
I'd be happy to put this on the wiki, but if you wanted to look it over
first, you are more
On Sep 8, 2010, at 2:34 PM, Kent Bower wrote:
That is for comparing *Clauses* and handles:
locations.siteid = :param_1
and
:param_1 = locations.siteid
However,
locations.siteid = :param_1 AND locations.locationid = :param_2
and
locations.locationid = :param_1 AND locations.siteid =
