No one with any response on this?
-- a.
Anders Steinlein wrote:
What's the recommended way of storing "tags" in a database, and then
filtering based on the existence, or *non*-existence, of those tags on
some entities?
Our application stores contacts, where each contact may
What's the recommended way of storing "tags" in a database, and then
filtering based on the existence, or *non*-existence, of those tags on
some entities?
Our application stores contacts, where each contact may have any number
of tags. We do this with the tables contacts, contacts_tags and tag
We have a database with contacts within lists, which can have any
number of tags associated with them. I would like to segment the
contacts based on any number of tag-based conditions, all of which
must be fulfilled (i.e. an ALL rule/filter). For instance, I want to
extract all contacts whi
On May 7, 2009, at 10:05 PM, Scott Marlowe wrote:
On Thu, May 7, 2009 at 1:45 PM, Anders Steinlein
wrote:
Hi,
I'm pondering a design question for a subscription-based web-app we
are
developing. Would it be feasible to create a new schema per user
account,
setting the search_pa
Hi,
I'm pondering a design question for a subscription-based web-app we
are developing. Would it be feasible to create a new schema per user
account, setting the search_path to their own schema during login?
There is no shared data (except where we keep a record of users), as
each account
