On 05/14/2013 02:22, Lycovian wrote:
A few months ago I watched a video conference where Mike demo'd some
optimizations for SQLAlchemy when using EAV schemas. Does anyone know
if these optimizations will make it into the product that we have
access to? I'm about to start a large EAV based
EAVs have a definite place and with judicious use they are extremely useful.
On May 14, 2013, at 4:37 AM, Julien Cigar jci...@ulb.ac.be wrote:
On 05/14/2013 02:22, Lycovian wrote:
A few months ago I watched a video conference where Mike demo'd some
optimizations for SQLAlchemy when using
On 05/14/2013 16:09, Michael Bayer wrote:
EAVs have a definite place and with judicious use they are extremely useful.
just curious: could you give an example where EAV is useful ?
On May 14, 2013, at 4:37 AM, Julien Cigar jci...@ulb.ac.be wrote:
On 05/14/2013 02:22, Lycovian wrote:
A
When you are storing data with key/values, where the set of keys is part of the
data. Storing configurational data is the main use case.HSTORE not an
option because it is postgresql-specific.
On May 14, 2013, at 10:49 AM, Julien Cigar jci...@ulb.ac.be wrote:
On 05/14/2013 16:09,
storing pickles in the database is an awful idea since your data is now
specific not just to Python but to the current shape of your object model at a
point in time. Storing JSON is not acceptable for the case where you need to
audit and version each user that has made changes to particular
On Tue, May 14, 2013 at 12:38 PM, Michael Bayer
mike...@zzzcomputing.com wrote:
storing pickles in the database is an awful idea since your data is now
specific not just to Python but to the current shape of your object model at
a point in time. Storing JSON is not acceptable for the case
On May 14, 2013, at 12:05 PM, Claudio Freire klaussfre...@gmail.com wrote:
On Tue, May 14, 2013 at 12:38 PM, Michael Bayer
mike...@zzzcomputing.com wrote:
storing pickles in the database is an awful idea since your data is now
specific not just to Python but to the current shape of your
Thanks for the reply.
Your example made me realize my model did not also use VARCHAR. Changing
the model column type to match the casting type made this work.
On Friday, May 10, 2013 3:57:36 PM UTC-4, Audrius Kažukauskas wrote:
On Mon, 2013-05-06 at 11:04:57 -0700, Glenn Yonemitsu wrote:
