Quoting [email protected]:
I know that in most all RDBMS are no implementations of lists or arrays.
On the contrary - and emphatically - just about every modern RDMBS supports collection types including lists, sets, multi-sets, and key-value data. This support has been in most databases for a decade now; most developers just don't know how to use it or are on platforms [like PHP] whose bindings go all bajiggidy when then encounter such a thing.
SQLAlchemy has excellent support for 'advanced' data-types.
When I want that I can use VARCHAR or something like that. And I can query for substr() in that field.
Ick. Better to use an HSTORE/JSON datatype - you can even index on them these days.
From 2013 - so the situation is much better now - but to get the general idea <http://www.wmmi.net/documents/PGSQL-Schemaless.pdf>
This is ok on a SQL-level.
No. It may 'work', but it is a HACK.
But what is about SQLAlchemy? I see nowhere a implementation of a List() type that encapsulate that VARCHAR-depending converting work? And I can not found something like thist over <https://duckduckgo.com>. But I imagine that some persons in the past invited something like that. Any hints?
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
