But my scenario is next:
I have a table of documents, a table of properties and a table of property values.
The initial approach to this was using a stored procedure that created a new column for each new property added in property table.
But when I transferred to the AR I simply mapped as many-to-many with value table.
Now my concern is the table size and it's performance.
Can I go like this with AR map?
The values table will grow like hell, what is your experience with this approach?
Thanks for any comments.
Mircea
On 6/17/06, Ayende Rahien <[EMAIL PROTECTED]> wrote:
I can think of several ways to make it happen, but I can't think of a
scenario where this is a good thing.
Self modifying schema is a near contester to self modifying code in by list
of things that I don't want to work with.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto: [EMAIL PROTECTED]] On Behalf Of
hammett
Sent: Saturday, June 17, 2006 4:33 AM
To: [email protected]
Subject: Re: [Castle-users] Use AR to dynamicaly create new table column
Hmm, I think this goes beyond what AR (and I dare to say, NHibernate) has to
offer.
On 6/16/06, Mircea Jivoin < [EMAIL PROTECTED]> wrote:
> Hy everyone,
>
> Does anyone know if it is possible to dynamically or somehow in
> run-time create new table column using AR or NHibernate?
--
Cheers,
hammett
http://hammett.castleproject.org/
_______________________________________________
CastleProject-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/castleproject-users
_______________________________________________
CastleProject-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/castleproject-users
_______________________________________________ CastleProject-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/castleproject-users
