Reg Me Please wrote:
Il Wednesday 21 November 2007 20:22:46 Joe Conway ha scritto:
Reg Me Please wrote:
The meaning is that an entity called by the value of "item" has a number
of properties called by "property" with value "prop_value".
So, for a single "item" there can be many different "prope
Il Wednesday 21 November 2007 20:22:46 Joe Conway ha scritto:
> Reg Me Please wrote:
> > The meaning is that an entity called by the value of "item" has a number
> > of properties called by "property" with value "prop_value".
> > So, for a single "item" there can be many different "property" each w
Reg Me Please wrote:
The meaning is that an entity called by the value of "item" has a number
of properties called by "property" with value "prop_value".
So, for a single "item" there can be many different "property" each with its
own value.
A filter is a list of property values needed to qua
Il Wednesday 21 November 2007 16:41:03 Rodrigo De León ha scritto:
> On Nov 21, 2007 9:21 AM, Reg Me Please <[EMAIL PROTECTED]> wrote:
> > Hi all.
> >
> > I've the following concept.
>
>
>
> This smells like EAV.
>
> Please read
>
> http://joecelkothesqlapprentice.blogspot.com/2006/04/using-one-ta
On Nov 21, 2007 9:21 AM, Reg Me Please <[EMAIL PROTECTED]> wrote:
> Hi all.
>
> I've the following concept.
This smells like EAV.
Please read
http://joecelkothesqlapprentice.blogspot.com/2006/04/using-one-table-vs-many.html
and consider reevaluating the schema according to valid relational
de
Hi all.
I've the following concept.
create table t_data
( property text,
item int8,
prop_value text
);
(I've cut some fields away needed only for data history).
The meaning is that an entity called by the value of "item" has a number
of properties called by "property" with value "prop_value"
