> But that would requires putting knowledge of fragmentation into your code, > which won't make things more flexible..
Flexibility and maximum performance are often a tradeoff, in all pursuits. :) Think cars. Anyway, fragmentation policy is usually something that's decided early and doesn't need to change (once you get skilled at picking fragmentation policies), and when striving for performance it's usually good for the code to be aware of the fragmentation policy the same way it's aware of the document schema(s). -jh- _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
