Default relative database filename to a sensible location

Bug #1206935 reported by Cris Dywan
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
U1DB Qt/ QML
Fix Committed
High
Unassigned
u1db-qt (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

As it is, the path of a Database can be literally anything. A relative path will put it wherever you happen to be running the application from, which is not very useful. A full path can be given, albeit there's no easy way to know it.

The relative path should by default be something like ~/.local/share/$APP_ID which would conveniently work under confinement and also be the right thing to do under a classic freedesktop.org system.

Full paths will still be allowed as they are and usable on the desktop, as will the special :memory: filename.

Related branches

Cris Dywan (kalikiana)
Changed in u1db-qt:
importance: Undecided → High
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:u1db-qt at revision 102, scheduled for release in u1db-qt, milestone 0.33

Changed in u1db-qt:
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package u1db-qt - 0.1.5+13.10.20130821.1-0ubuntu1

---------------
u1db-qt (0.1.5+13.10.20130821.1-0ubuntu1) saucy; urgency=low

  [ Christian Dywan ]
  * Use QStandardPaths to find a good path for relative filenames. (LP:
    #1206935)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 102
 -- Ubuntu daily release <email address hidden> Wed, 21 Aug 2013 16:18:56 +0000

Changed in u1db-qt (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.