Storing objects in relational database

[bruno.desthuilliers at gmail.com]

On 24 mai, 13:01, Piotr Chamera <piotr_cham... at poczta.onet.pl> wrote:
> bruno.desthuilli... at gmail.com pisze:
>
> > I don't know if you'd label it 'elegant', but as far as I'm concerned,
> > storing serialized objects as blobs in a relational database is mostly
> > non-sense. If I use a relational database, it's because it is a
> > *relational* database. If you want an OODB, then we have the ZODB,
> > Durus and a couple others.
>
> It is sometimes convenient to store objects in mature relational
> database backend (reliability,  stability, support, tools,
> replication, etc.). See latst efforts with RelStorage backend
> for ZODB (http://wiki.zope.org/ZODB/RelStorage) - it stores
> pickled Python objects in Oracle, PostgreSQL or MySQL)

You mean a SQL database backend here - the conveniences that you
mention have nothing to do with being relational or not. And that's my
point: pickling objects, you loose of the convenience of a
*relational* database.