In gql.py method _create(self): around line 242
where it does
self._tableobj = classobj(self._tablename,
(google_db.Model, ), myfields)
I'm going to make a copy of myfields into my own
myfields_Augmented_With_PHANTOM_GAE_Fields
and on that augmented list I'm going to add a field of type
google_db.SelfReferencingProperty
because I need it to implement a treeview
So I will change line 242 to:
self._tableobj = classobj(self._tablename, (google_db.Model, ),
myfields_Augmented_With_PHANTOM_GAE_Fields)
This way, the GAE specific field will be carried along with the web2py
rows, and web2py will not know it
and thus I can still use the rows with regular web2py relational
methods (and get all the usual benefits)
and yet I will have certain extra GAE-specific fields which I can
handle with native GAE code.
I think this approach is better than waiting for web2py to add a GAE-
specific support into the DAL.
GAE Native code is already python and is very easy to use and is very
similar to the syntax of
the web2py DAL, so I see no need for specific web2py GAE type support
except I would like to have this feature
for adding in a 'PHANTOM' GAE-specific field as I have described
above.
Anyway, I am going to go ahead and do this on my private machine...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
