Michael,
I took a look at the recipe you indicated, it looks promising but the check
should be constructed from database results. Another issue is that this project
is implemented in my web based desktop/Os which uses SQLAlchemy from the bottem
up. So modifiing the session object globally is
On Feb 8, 2011, at 6:05 AM, Martijn Moeling wrote:
Michael,
I took a look at the recipe you indicated, it looks promising but the check
should be constructed from database results. Another issue is that this
project is implemented in my web based desktop/Os which uses SQLAlchemy from
Michael,
Thank you,
The final solution has nothing to do with ACL's or addresses and security for
others getting results by querying is a none issue.
As mentioned before I am building a database and tools to help chemists
selecting molecule structures. It is all way more complex than you might
Hi,
It is me again with an interesting thing, I've searched the net, this group
etc. Not a lot of people seem interested in append_result, I AM!!
I am looking for a way to implement the following:
I have many tables, a lot with polymorphic inheritance and self and cross
references.
In order
On Feb 7, 2011, at 10:55 AM, Martijn Moeling wrote:
Hi,
It is me again with an interesting thing, I've searched the net, this group
etc. Not a lot of people seem interested in append_result, I AM!!
I am looking for a way to implement the following:
I have many tables, a lot with
I think, I might be helped with the create_instance event
I will never ever stop a class from being saved/persistent,
it is the other way around. I thought I was able to use joins and or relations
to limit for allowed results from a query.
With all the polymorphic and self references I have
On Feb 7, 2011, at 11:42 AM, Martijn Moeling wrote:
I think, I might be helped with the create_instance event
Assuming you're talking about when the ORM establishes an instance from a newly
fetched row, you can use the @reconstructor hook for that. 0.7 publishes this
event additionally as
