Hi Tullio,
When you use MemoryDB, it means that you will always loose on startup all
installation.
Just because it was kept in Memory and nothing can be persisted for a restart.
Using Memory DB for development makes only in some situations sense, for
example that you're not interested in persisting anything but testing something
which needs high performance you couldn't have otherwise bound to a bad
filesystem on a laptop (not comparable to a huge Oracle DB server).
Using a MemoryDB just means, every time you restart the complete system will
install again, and again, and again.
As Matthew wrote, the {{magnolia.update.auto}} property defines if the system
automatically does the update or you need to push on the install screen the
installation.
Mgnl-bootstraps:
The you need to place for EVERY change you've done in JCR a xml export file to
persist it when repo (the DB) is deleted and/or the module is reinstalled.
But in you case this is on every startup. Usually a developer needs to do that
before deleting the repository manually.
So I don't see any gain for you using the Memory DB instead of the derby
database for development.
Derby stores all on your filesystem in a embedded DB.
If you want to reinstall, delete the repository. You can copy it too and switch
back if wanted, so its a bit more flexible than MySql for development. Its just
a folder with files in your file system.
Regards
Christian
On Dec 13, 2010, at 7:50 AM, Tullio Bettinazzi wrote:
>
>
> I didn't find any error during migration.
> The parameter magnolia.update.auto is set to false, previously it was true
> but the startup failed as I indicated at the beginning of this thread.
> I understand thata, running in memory I sholuld save something in
> mgnl-bootdtrap but I don't know what, could You help me ?
> Tks
> Tullio
>
> --
> View this message in context:
> http://old.nabble.com/Upgrade-to-4.4---Fails-tp30350370p30443001.html
> Sent from the Magnolia - User mailing list archive at Nabble.com.
>
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
