I am in to same situation and untill now I realized the simpler solution is use GAE option in DAL and develop running web2py directly (admin works), test with devappserver (admin does not work) and deploy with appcfg when done. It is less invasive, maybe a little tricky, but I have not gone so far yet.
On Aug 19, 2:59 pm, Yarko Tymciurak <[email protected]> wrote: > great - looking forward to seeing your work... > > > > On Wed, Aug 19, 2009 at 12:24 PM, dlypka <[email protected]> wrote: > > > I believe it is possible to have a hybrid model. I have one working > > (to some degree). > > My approach is not related to the column-oriented aspect. I'm working > > at the GAE datastore CLASS level, not BigTable low-level. > > So I am pushing ahead with it, and anyone who is interested may > > contact me for code. > > > On Aug 19, 12:25 pm, Yarko Tymciurak <[email protected]> wrote: > > > There are 2 things to keep in mind here: > > > > Specificity (big tables) and abstraction (portability, DAL). > > > > Right now, the data abstraction layer of web2py (DAL) handles RDBM's > > rather > > > close to the RDBM (that is, it is not an object-relational mapper, but a > > bit > > > lower level). It also handles those concepts from that abstraction > > which > > > map well into big tables. DAL also creates freatures (form generation, > > auth > > > tools, etc.) based on DAL information. > > > > IF you make BT (big table) specific adaptations, you will [1] risk losing > > > the abstractions and the interface into web2py facilities. But it may > > be a > > > useful start. A better start would be to look at what abstractions DAL > > > employes, what the interfaces to the rest of web2py are, and create an > > > interface class for "COLUMN ORIENTED STORES" (e.g. start with just big > > table > > > if you want). This would be more interesting results than merely "I > > want > > > to access all of big tables facilities" - it would reach into how to hook > > it > > > into the nature of what web2py does. > > > > On Wed, Aug 19, 2009 at 11:20 AM, dlypka <[email protected]> wrote: > > > > > rdbm is still needed to drive CRUD forns > > > > > On Aug 19, 11:56 am, Carl <[email protected]> wrote: > > > > > Google's own video are a place to start: > > > > > > Wipe your mind of rdbm design, sit back and breath them in... > > > >http://www.youtube.com/watch?v=tx5gdoNpcZMhttp://www.youtube.com/watc. > > .. > > > > > > On Aug 19, 4:28 pm, Benigno <[email protected]> wrote: > > > > > > > Hello Carl, > > > > > > > My question was rather more generic, I mean from an application > > > > > > design point of view, what things does one need to consider when > > > > > > creating an app for GAE. I was asking about Rdb, because thats the > > > > > > only db structure I have been working with all my life so it would > > > > > > have been more "intuitive" for me to understand the concepts. > > > > > > > On Aug 19, 2:36 pm, Carl <[email protected]> wrote: > > > > > > > > hi Benigno, > > > > > > > > 'fraid my project is from a clean sheet so I've not investigated > > how > > > > > > > to migrate relational databases. > > > > > > > I'm currently looking athttp:// > > code.google.com/p/app-engine-patch > > > > > > > which leverages Django to access BigTable natively. > > > > > > > > C > > > > > > > > On Aug 19, 12:52 pm, Benigno <[email protected]> wrote: > > > > > > > > > Carl, > > > > > > > > > Sorry I do not add any answer. I would be delighted to > > hear > > > > more > > > > > > > > about the subject, as it is indeed quite important for me too. > > > > > > > > > Can you address me to any place to learn more about > > bigtable?. > > > > > > > > Rather, what are best practices and how to "transform" an Rdb > > > > > > > > structure into something that works for bigtable. > > > > > > > > > Cheers, > > > > > > > > Benigno. > > > > > > > > > On Aug 18, 1:37 pm, Carl <[email protected]> wrote: > > > > > > > > > > hi > > > > > > > > > > I'm currently building a project with python, web2py & > > pyjamas; I > > > > will > > > > > > > > > be deploying on gae. > > > > > > > > > > As you will know gae isn't a relational store but leverages a > > > > > > > > > different design so I want to experiment with two different > > > > > > > > > approaches: a) accessing gae thru web2py (treating gae as a > > > > subset of > > > > > > > > > a relational db) and b) accessing bigtable more directly to > > help > > > > my > > > > > > > > > data accesses scale on google's infrastructure. > > > > > > > > > > Now core to web2py's philosophy is compatibility for code > > across > > > > a > > > > > > > > > range of data stores. I realise my option b) **may not** be > > > > compatible > > > > > > > > > with that goal (perhaps this is where the new DAL comes in?). > > > > > > > > > > finally the question: has anyone implemented bigtable > > directly > > > > while > > > > > > > > > still using web2py and if so, how do they do local testing?- > > Hide > > > > quoted text - > > > > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
