26 Jul
2010
26 Jul
'10
6:42 p.m.
My understanding is large or many attachments can cause problems for HSQL
so I would be on the safe side and switch to Postgres because it is a pain
to have a database large enough that it causes the import/export system problems
and then have to use a large export tool and hope for the best.
Also in my experience installing on Postgres is very easy (especially on a Linux
system where you can install Postgres with the package manager) The only limitation
is you can't have multiple sub-wikis with Postgres.
Caleb
Aleks87 wrote:
Marius Dumitru Florea wrote:
On 07/08/2010 04:00 PM, Aleks87 wrote:
I plan to use it in an intern network. About 7 people would use it for
knowledge exchange. That means that they can create owen wiki pages and if
necessary they can add attachments. But there will also be a "TodoClass" and
similiar to the Todo a ToolClass where the user can post usefull tools.
The Event Calendar is also included to add meating dates and the
PhotoAlbumsClass to add photos from the last party^^ (don't know if we would
use it, cause its very exhausting to add all the photos individually).
My Database is now about 35MB and I,ve only created a few test pages. I have
to add 75MB KnowHow saved in word, excel and text editor files...don't know
how much MB it would be if I copy the content of the files in a wiki page.
Some files I'll only attach because it takes to long to copy, paste and
modify all the text.
How much MB can HSQLDB handle? Where can I change this value? And would you
advise me to use another database? I have installed the standalone version of XWiki
Enterprise 2.4 M1
The standalone installation have a HSQLDB Database which I should not
use.
Is it right?
It all depends on what you plan to do with your wiki. If you just
want
to play with it, test it, or even use it internally for a few people
then HSQLDB is fine. If you plan to make it public on the web or an a
wide network then it's recommended that you switch to a more reliable
database.