BUG - Local MySQL in GAE

[webm...@trytha.com]

GAE can access/edit MySQL locally through web2py.  However, since web2py writes the DB metadata to app/databases, the .table files end up stored in GAE virtually (in a table called web2py_filesystem, which preserves the file path as well).  Web2py does not seem able to access this table when it comes time to read from /databases.

Is this an actual bug (i.e. need to edit the framework) or is there some method to get the DAL's "folder=path" connection option to properly find the web2py_filesystem table?  I tried folder='$HOME/app/databases' (the path GAE creates for web2py_filesystem entries) with no success.

I tried posting this in web2py-users, but it seems like more of a developer issue (assuming it's a bug).  I just want to know if it's a bug so I can stop looking for a solution and try to find a workaround.  Seems like there should be some easy fix given that everything works on GAE's servers.

[Massimo DiPierro]

No you do need to mess with folder=….

I am suing google sql on dev_appserver right now without issues. The .table are stores in the virtual fs on mysql.

I think you have an old pydal.

 

--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-d...@googlegroups.com
unsubscribe: web2py-develop...@googlegroups.com
details : http://groups.google.com/group/web2py-developers
the project: http://code.google.com/p/web2py/
official : http://www.web2py.com/
---
You received this message because you are subscribed to the Google Groups "web2py-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py-develop...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.