Re: Keeping schema static as objects are added

From: <sergei.sheinin_at_gmail.com>
Date: Tue, 27 Nov 2012 19:38:48 -0800 (PST)
Message-ID: <1a1ac63d-ecd1-4256-9746-7ee18bef5f53_at_googlegroups.com>

> EAV is a bad bad bad bad bad bad bad bad idea, and if your language has
> no use beyond dealing with EAV, then it is at best pointless.
>
>
>
> Eric
>

EAV is used in the platform to keep hierarchical metadata and program code. Same mechanism accommodates table data as a feature and interfaces with 3NF tables.

My lesson from posting here is that I must do a better presentation of a language of higher level in respect to procedural SQL and with ability to update programming logic without affecting underlying schema. Storing app data in EAV is not what I set out to do (I did it first time one dozen years ago). Thanks everyone. Received on Wed Nov 28 2012 - 04:38:48 CET

This message: [ Message body ]
Next message: vldm10: "Re: some information about anchor modeling"
Previous message: vldm10: "Re: NTriples DBPedia from Musatov thank me later"
In reply to: Eric: "Re: Keeping schema static as objects are added"
In reply to Eric: "Re: Keeping schema static as objects are added"
Next in thread: Arthur Ward: "Re: Keeping schema static as objects are added"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message