Forum Subject: Full pathnames in DB

Posted on: 04/06/10 03:29pm
By: Anonymous (PJP)

I don't know when it happened, or if anyone has complained about it, but sometime between 1.4.x and 1.5.x someone placed full pathnames in the database.

It used to be the case that you could relocate everything simply by changing the pathnames in the config files. Now that doesn't work.

You have to export the db and look through with an editor to find the embedded names and change them -- just to make life more interesting, there is also a field specifying the length of the pathname string, so you have to correct that too.

There really is no reason to embed full pathnames in the db.

Re: Full pathnames in DB

Posted on: 04/06/10 03:40pm
By: Dirk

The handy Migrate[*1] option in the install script will take care of that

bye, Dirk

Re: Full pathnames in DB

Posted on: 04/06/10 03:55pm
By: Anonymous (PJP)

I still see absolutely no reason why full pathnames should be embedded in the database.

Just seems lazy to me ....

Re: Full pathnames in DB

Posted on: 04/06/10 04:02pm
By: Dirk

Feel free to submit a patch (you knew this would be coming, right?

bye, Dirk