Hi. I'm working on a project and I'm using ZODB but my mentor advices me
that this model of database will be so big after one or two years. He
consider that because ZODB works with transactions and it's added to
ZODB frequently. My mentor mentioned me PostgreSQL, but I don't want it,
because is bet
Hi. You do not have to have to sacrifice an object database to use
postgres. You may wish to look at pgstorage for your backend and have
best of both worlds. See:
http://sourceforge.net/projects/pgstorage
I am hoping to eggify this before long and bring it into a namespace
package to make it
Am Montag, 23. April 2007 15:21 schrieb Ariel Eduardo Morales Malpica:
> Hi. I'm working on a project and I'm using ZODB but my mentor advices me
> that this model of database will be so big after one or two years. He
> consider that because ZODB works with transactions and it's added to
> ZODB fre
"- RDBs scale scale very well, so in case your application gets really
huge, an RDB is an option. With Zope, you can easily cluster the
application server, however the ZODB can not be distributed. (Maybe ZODB
can even not make good use of multiple processor due to Python's GIL)."
You can use Zope
Hermann Himmelbauer wrote:
I'm no expert, but I don't see how transactions would lead to a huge database.
I suspect he is referring to the way FileStorage use an append-only file
format (between packs). If you never pack the database, it will grow
forever. The simple answer is "don't do tha
Hi,
As already mentioned before, I use interfaces that contain lists of other
interfaces via the following syntax:
emails = List(value_type=Object(schema=IEmail))
In my formlib-based class, I have use the following, so that the widgets are
displayed correctly:
email_widget = CustomWidgetFactor
