Thanks a lot. The link really helped -Nichi Alexander Klimetschek wrote: > > On Thu, Mar 19, 2009 at 8:44 PM, Nichi <[email protected]> wrote: >> Say, I have two tables Experiment and ExperimentData that I want to store >> using Jackrabbit’s content repository.  Experiment has around a thousand >> rows and ExperimentData tens of millions of rows. There is a one-to-many >> relation between Experiment and ExperimentData. >> My understanding is that each of these tables will be the node types and >> rows in these tables would be the nodes, columns being their properties. >> The >> reference property would be used to implement the one-to-many relation. >> Is my interpretation correct? Could there be a problem because of the >> large >> size of the database ? > > A "generic" mapping like tables = node types and rows = nodes would > imply you get flat hierarchies with millions of child nodes of one > "experiments" node. This is inefficient in Jackrabbit (we estimate the > max. recommended number of child nodes per node at 10K). And > completely misses the advantages of JCR modeling. You should rather > find a good hierarchy for your data. Almost always working is the date > of the item, creating subnodes like "2009/03/20/mydata1". > > See also http://wiki.apache.org/jackrabbit/DavidsModel > > Regards, > Alex > > -- > Alexander Klimetschek > [email protected] > >
-- View this message in context: http://www.nabble.com/Datastore%28MySql%29-tp22587989p22674246.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
