El miércoles, 15 de julio de 2015, 6:09:26 (UTC-3), Massimo Di Pierro escribió: > > web2py include pydal and pydal is an API for accessing RDBMs and some > NoSQL engines. This is not your use case. > > web2py does not include a OODBM but nothing prevent you from accessing one > and take advantage of all the other features. You simply would not do it > through the DAL. The reason is that there is no standardize API for > accessing OODBMs. Every one of them is different and every one has its own > set of APIs. > > This is weird to read as there is the ODMG Standard http://www.odbms.org/odmg-standard/ which produced also OQL, ODL, etc.
> So for example in the python world a popular one is ZODB. You can install > ZODB and use it with web2py. I do not expect any problem but I never tried > it. There are other OODBMs which you can use from python. If they work with > Python, they work with web2py. > > Thank you for the reference to ZODB. However, using an OODB would miss the SQLFORM and SQLFORM.factory features right? > That said. I disagree that OODBMs are the future and SQL is the past for > two reasons: SQL databases are still widely more popular and more scalable. > It is possible to build a OODBM on top of SQL database, and in fact, if > time permits, I would like to build one on top of the web2py dal. > > > I do not want to promote a flame war here, but I didn't said SQL is the past (even though that could represent a common perception about relational databases today). However COBOL is also used today although many languages (including python) were invented later. The same way, OODBMs were invented for specific reasons - everything has been widely documented in documents like "Hitting the relational wall" http://www.odbms.org/wp-content/uploads/2013/11/029.01-Wade-Hitting-the-Relational-Wall-2005.pdf and if python is object-oriented, it makes sense to persist domain objects in object-databases. > On Wednesday, 15 July 2015 03:29:04 UTC-5, Esteban Bulutsuzku wrote: >> >> Hello, >> >> I am an experienced OOP programmer. I -fortunately- do not use relational >> technology anymore, so I won't plan get back to write SQL/RDBMS/ORM stuff >> (I really don't care if the relational math theory + ISO/IEC 9075-1 backs >> the stack). This could sound like a rare use case for you, but it is not if >> you use actively other systems (Java, db4o, GemStone, etc) where you can >> have nested complex designs with navigational access to data, dynamic class >> definitions, class extensions, etc. Also if you don't ever plan to use an >> OODBMS, sometimes is desirable to delay the need to hook up a database >> during development, or ever forever ;) >> >> But I am dissapointed, because after hearing a lot about web2py I still >> have not found how to work with web2py with an OODBMS (any of them). It >> seems that web2py is tied to RDBMS (which to me is technology from 1970's >> but that's another story). >> >> Maybe most python devs have experience with flat simple tabular data >> models, it could also be the case that Python file-orientation promotes >> more scripting approach than object-technology, and I am not criticizing >> you but in my case I already have a rich object model (is *NOT* NoSQL) and >> I am giving web2py a chance. >> >> But it seems there is few to none documentation of web2py + OODBMS, i.e. >> how to use the DAL with a OODMS backend. >> >> Is web2py still valid for my use-case? >> Anyone working with OODBMS and web2py? >> >> Thanks, >> Cheers, >> >> Esteban >> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
