Version Migration

[David T.]

The biggest problem with the database back end is users' misconception that its use implies database functionality. They think it will allow them to perform database actions on the data set,  as well as have multiple users simultaneously. As you know, neither of these is true at this time. 
David

 
 
  On Wed, Aug 30, 2017 at 1:04, Colin Law<clanlaw at gmail.com> wrote:   On 29 August 2017 at 19:12, D <sunfish62 at yahoo.com> wrote:
> ...
> The database back end is stable, and has been for a while now. There is
> nothing to prevent a user from making use of it, even for production.

OK, but note the OP is going to use 2.6.15, which was released in Dec
2016 I believe. I don't know whether there have been any significant
sql related bugs since then.

Even if not, then it cannot be denied that the xml backend has had
vastly more use than the sql backend. Certainly anyone using a db
should make sure they take regular backups of the db (which can be
trickier than just copying the xml file).

Colin