[DUG] Runtime user defined fields

[russell]

Consider reasons for not allowing users to add fields to tables using "alter
table".
1. The max number of columns in a table is say N whereas the max number of
rows in a column is say 2**N. Each DB kind will have its limits.  Rohit's
method gives you room to accommodate a user with a hunger for new fields.
2. (Already mentioned) In your user land all users will have the same
architecture in their DB file. (no unnecessary maintenance problems?)

R



-----Original Message-----
From: delphi-bounces at listserver.123.net.nz
[mailto:delphi-bounces at listserver.123.net.nz] On Behalf Of Steve Peacocke
Sent: Wednesday, 6 March 2013 3:23 p.m.
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] Runtime user defined fields

Mind you - Rohit's implementation does also have the advantage of adding
"Active", and dates to each new field. Quite useful even considering that
I'll also have an Audit table.

Damn, where's that definition of "simple". 

Steve 

On 6/03/2013, at 1:36 PM, Leigh Wanstead <leigh.wanstead at gmail.com> wrote:

> Hi Steve,
> 
> I like Rohit's suggestion.
> 
> There is another way to add a blob field and using format is xml to 
> contain all extra fields.
> 
> Regards
> Leigh
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at listserver.123.net.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at listserver.123.net.nz 
> with Subject: unsubscribe

_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi at listserver.123.net.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to delphi-request at listserver.123.net.nz with
Subject: unsubscribe