Christian,
That is helpful. Basically you've confirmed my initial analysis that
because BaseX databases are light weight that keeping things simple is the
most appropriate choice.
If I was doing things at scale of course I'd do performance testing to see
where the bottlenecks are, but that is
Hi Christian,
do you have any idea on the performances of the users module that comes with
BaseX? Does it work properly with a count of users up to several hundreds?
thousands? Any tests done so far?
Thank you.
BR,
Marco.
Hi Marco,
do you have any idea on the performances of the users module that comes with
BaseX? Does it work properly with a count of users up to several hundreds?
thousands? Any tests done so far?
I don't believe you should run into troubles here. I haven't done any
performance tests so far,
Hi James,
try {
db:replace(“DATABASE_NAME”,”PATH/TO/FILE”,Element/)
} catch * {
db:output(insert code here)
}
Unfortunately, due to the semantics of XQuery Update, there is no
chance to make this work, because all updating functions will first be
moved to the pending update
4 matches
Mail list logo
