all of these approaches i think are easier than making a subclassed
Mapper.


Yes, they are indeed. I'll pick  either of them.

I could also add another mapper flag to be used in conjunction with
column_prefix called "query_prefix" that just allows the "_" to be
stripped during get_by/select_by operations, like the extension would
do.


If my requirements are met by an extension, that will surely suffice. I've seen the  mapper extensions has a complex constructor already, no need to add an additional keyword argument for such a 'niche' task as mine is.

I dont understand why the Mapper needs to know about these
attributes, if they are not related to database columns or other
database-mapped relationships.

I think that it came from a misunderstanding of mine; I probably haven't grasped yet all of sqlalchemy's internals.
I thought it was the mapper who mapped the UOWProperty to the class columns, but after debugging for a while I'm not so sure about that. My problems also arise from the fact that it doesn't seem there's any UOWProperty attached to the class till the first instance of the class is created (or pulled from the db), so I might just have looked into the wrong code.

My idea was that the mapper would just have read that values from the class and used them to properly 'instruct' the ExtProperty I wanted to use.

BTW, the solution you found seems to be the best and has no shortcomings, so I'll take that route.

Thank you for both your help and sqlalchemy itself :-)


--
Alan Franzoni <[EMAIL PROTECTED]>
-
Togli .xyz dalla mia email per contattarmi.
Remove .xyz from my address in order to contact me.
-
GPG Key Fingerprint (Key ID = FE068F3E):
5C77 9DC3 BD5B 3A28 E7BC 921A 0255 42AA FE06 8F3E
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sqlalchemy
-~----------~----~----~----~------~----~------~--~---

Reply via email to