|
I would recommend that you would use solution 1. From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mircea
Jivoin Ayende, thanks for the
response. On 6/18/06, Ayende Rahien <[EMAIL PROTECTED]> wrote: A table with 63 columns is not
pretty. I'm going to assume that it is mostly nullable ones, which is even less
pretty. Use your first suggestion, you will be happy. Check NHiberntae caching. There
is some info about that. There is a short guide here: http://www.castleproject.org/index.php/ActiveRecord:How_to:Enable_second_level_cache From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Mircea Jivoin
That's good to hear, I have a set of 63
properties for each document. On 6/17/06, Ayende Rahien < [EMAIL PROTECTED]> wrote: This shouldn't have much
effect. I'm using similar methods in several places, and I have not seen any
perf problems. In general, the DB should
handle this easily, it is a join and a select, simple stuff mostly. Throw some caching into the
deal, and you will have smooth sailing. How often are you adding a new
property, anyway? Does it make sense to have dynamic properties? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
] On Behalf Of Mircea Jivoin
Yes is a nasty thing to do. 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
|
_______________________________________________ CastleProject-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/castleproject-users
