pp wrote: > > > Ok, this is clear now. Well, it is a good idea. I just have a bad > > feeling to put everything in midgard what are not related. Moreover, > > there will be about 5-20 parameters for each of articles (and there will > > be tens of thousands of articles), and there are thousands of persons, > > with similar number of params I suppose. I wonder what performance will > > give the system if there are, say, a million rows in parameters table? > > So, if I have the possibility to get out part of the data, I will > > utilize it. > > hmmmmm..... I always thought that database is just for that: > "grow up, grow up" :)
If I have the possibility to partition my data space, I do it. > I do not see any sense of doing anything if I am to carry about > of my database size. If it will grow that way it will slow down all > operations , I will change server components. Well, parameters are used everywhere in midgard. If I fill it with user data stuff, I will slow down article handling, admin ui either... > And what is more , using midgard for 100-200 pages looks like > using MS Word to write "hello" :) Well, I use MSWord exactly for that. :-P > > It is a solution if you are the content author. If there are another > > companies who write the pages (say, an extended way of webhosting), > > there is no way to use active pages for ordinary pages. > > Content author? But if You want to implement midgard based forum, > then user who create message is an author! Yes, sort of. But if I use an add-in forum solution, then these contents are in a separate database, so why their authors should be in midgard...? > I think that midgard based portal will be still faster then for example > PHPNuke. I still don't know PHPNuke. Fery --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
