[Dbix-class] solving problems with data driven design (was Re: Dynamic constraints on PostgreSQL arrays)

[Darren Duncan]

At 12:04 AM +0100 11/10/05, Kaare Rasmussen wrote:
>  > A much simpler, and more portable, solution is to use multiple joined
>>  tables instead.  If you want certain degrees of user-definable
>
>Sorry. Fail to see the simplicity. All I want is to remove "references"
>constraints from my code and push it down. It's not really easy to implement
>it in the database, as I really don't know the possible dimensions by now.

The simplicity of using joined tables over arrays in table fields is 
that each table field holds only a scalar rather than something 
arbitrarily complex.  And databases are really good at working with 
those kinds of tables.

I can't really suggest much more unless you better describe what kind 
of data you are wanting to store and how it relates to each other.

>But I think that I have to put a "no" for this question.

If you want.

>  > This isn't quite the same problem, but here's an incomplete example
>>  schema for a simple but flexible product inventory system.  The same
>
>Are you interested in building an OSS ERP ?

Sort of.

I am making a commercial product which could be adapted to do that 
among other tasks, but it won't be specific to ERP; rather, it is a 
general data and/or resource management tool.  Also, it won't be OSS 
initially, but will become that later when I'm confident I can earn 
enough from just support contracts.

-- Darren Duncan