A new predefined simplified layout has been added with the only the basic
functions: schema, browsing and SQL execution. Ideal for courses.
Also added options for moving all the docked windows to the bottom, left
side or top (for the right, the default can be restored with Reset Window
Layout as before).
See issue #2307
This adds the possibility to handle network replies individually instead
of routing all of them through a central handler routine. The
centralised approach made the code more complicated than necessary and
would inevitably lead to confusion when sending similar requests
simultaneously.
This splits up the RemoteDatabase class into two classes, RemoteDatabase
and RemoteNetwork. The first is for managing the directory of cloned
databases while the second is for network handling only. Moving the
network code into a separate class requires some rewriting but should
make the code easier to maintain and extend.
This adds a new context menu action to the commit list in the Current
Database tab of the Remote dock which downloads the database from that
commit and saves it to another file. This file can then be opened and
inspected just like any other database file and does not update the
local clones data.
This adds a new toolbar action to the Current Database tab of the Remote
dock which downloads and updates to the latest commit of the currently
opened database and branch.
This adds context menus and some context menu actions to all the tree
views in the Remote dock. No new features are added. This just adds a
new way to trigger existing features but also establishes a place for
future actions for new features.
Make sure to only show a warning that local changes might be lost before
actually downloading a database and overriding the local copy. When we
just open the local copy, no warning needs to be shown.
Instead of always selecting the default branch select the currently used
branch in the Push Database dialog. Only default to the default branch
if no current branch is available.
After opening a clone of a remote database, allow checking out the
different branches and commits of this database in the Current Database
section. This way you access all branches and see their history in DB4S.
Move the Clone database button to a newly created tool bar in the
DBHub.io tab of the Remote dock.
Transform labels in the Current Database tab into line edit widgets.
Adjust spacings a bit.
Complete translation and some improvements:
- Fix warnings raised by Linguist
- Avoid Title Case in Spanish
Issue #2124
Cherry-picked from v3.12.x branch.
# Conflicts:
# src/translations/sqlb_es_ES.ts
Add a toolbar to the Current Database tab of the Remote dock with one
button for now. This button opens the web page of the currently opened
database in the browser.
Also reduce the margins in the Remote dock a bit.
This makes the database name columns a bit wider by default. It also
reduces the width of the size columns, moves the commit id column to the
end of the remote table, and hides the file name column in local table.
See issue #2334.
This fixes a sporadic crash when selecting an identity in the Remote
dock. It happened because selecting an identity removes the first dummy
entry in the drop down list of identities which for some reason emits
the signal which then calls the same function to update the root dir
again. Depending on the timing of the network requests this could lead
to some confusion when building the tree structure.
Also fix an off-by-one error when building the tree structure.
See issue #2333.
This avoids possible confusions when getting the currently opened
database file. After closing a database this would return the previously
opened file when in fact no file is opened.
See issue #2334.
When the CSV import fails because of an unexpected end of file show a
better error message. When the file ends but we are still expected more
data to come, i.e. we are still in quote mode, no INSERT statement
failed. So showing the last SQLite error message will never show you a
proper error message. Instead tell the user that their settings might be
wrong or the file malformed.
See issue #2330.
This adds a new button to clone databases using a direct link which is
useful when you know which database you want to clone and do not want to
browse through the list of all databases in the Remote dock. Generating
this link still needs to be added to the DBHub.io web UI.
Because there is no local file on the disk to upload in-memory database
cannot be uploaded to the remote server. This commit makes sure the
button to upload databases is disabled for in-memory databases. It also
fixes a problem where some information on a previously opened database
would remain visible when opening an in-memory database.
When pushing a database to the remote server only provide the commit id
when the database file is saved in the directory of cloned databases.
This makes sure we do not provide any random commit id when a database
with the same name as a cloned database is pushed.
See issue #1164.
Highlight the last locally known commit id in the commit list in the
Remote dock. This should make it more obvious whether there are any
newer commits on the server.
When opening a clone of a remote database show a list of all branches,
releases, and tags in the Remote dock and show the commit list when
selecting one of them.
