Issue 410 in simal: Simal database non-portable?

[si...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect

New issue 410 by Stev...@gmail.com: Simal database non-portable?
http://code.google.com/p/simal/issues/detail?id=410

I want to do development on one machine, and deploy to another. So I copied
my whole development directory, to the deployment machine (new directory),
and did the same with the simal_TDB directory.

What I've noticed so far:
1) All the projects (a few hundred) are show up ok in the list views, but
clicking any of them gives "No project with that ID found"
2) All people show up ok in the list views, but clicking on any of them
(person/simalID/per1412) takes you to a list of all people (but not the
actual PersonBrowserPage - there's no letter index, for instance)
3) simal.nextPersonID and simal.nextProjectID are both stored in
local.simal.properties, rather than in the database itself. This seems
likely to cause someone pain one day.

[si...@googlecode.com]

Comment #1 on issue 410 by Stev...@gmail.com: Simal database non-portable?
http://code.google.com/p/simal/issues/detail?id=410

I should mention that the dev machine is XP, the deployment machine is
Linux, and used WinSCP to copy the files. I've just tried transferring
the .info files as text, but that doesn't seem to have changed anything.

[si...@googlecode.com]

Comment #2 on issue 410 by Stev...@gmail.com: Simal database non-portable?
http://code.google.com/p/simal/issues/detail?id=410

(At the risk of being spammy, I will mention that this is not a blocker for
me in any way. All the data in the database is being mass-imported, so it's
easy for me to just perform the import on the server, instead of
transferring the database.)

[si...@googlecode.com]

Updates:
Status: Duplicate
Labels: -Type-Defect Type-Enhancement
Mergedinto: 304

Comment #3 on issue 410 by ross.gardler: Simal database non-portable?
http://code.google.com/p/simal/issues/detail?id=410

Simal databases are not intended to be portable see Issue 190.

This issue is a duplicate of Issue 304

[si...@googlecode.com]

Updates:
Mergedinto:

Comment #4 on issue 410 by Stev...@gmail.com: Simal database non-portable?
http://code.google.com/p/simal/issues/detail?id=410

Um, not really seeing the connection with Issue 190, but ok.

[si...@googlecode.com]

Comment #5 on issue 410 by ross.gardler: Simal database non-portable?
http://code.google.com/p/simal/issues/detail?id=410

The relationship to Issue 190 is that it justifies and explains the design
decision that means the databases are not portable. The linked data is, but
not the database itself.

Issue 304 is about addressing these issues from a backup point of view.