search

HughP / simal

Automatically exported from code.google.com/p/simal
0 stars 0 forks source link

Simal database non-portable? #410

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
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.

Original issue reported on code.google.com by Stevage on 14 Mar 2011 at 2:43

GoogleCodeExporter commented 9 years ago 
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.

Original comment by Stevage on 14 Mar 2011 at 2:46

GoogleCodeExporter commented 9 years ago 
(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.)

Original comment by Stevage on 14 Mar 2011 at 3:14

GoogleCodeExporter commented 9 years ago 
Simal databases are not intended to be portable see Issue 190.

This issue is a duplicate of Issue 304

Original comment by ross.gardler on 14 Mar 2011 at 2:11

GoogleCodeExporter commented 9 years ago 
Um, not really seeing the connection with Issue 190, but ok.

Original comment by Stevage on 16 Mar 2011 at 9:37

GoogleCodeExporter commented 9 years ago 
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.

Original comment by ross.gardler on 16 Mar 2011 at 2:43