Skip to content

Releases

Nightly build (develop)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 08:50
b9913e8

Added

  • An availability group can be failed over from its context menu: Fail Over…. Pick the replica to
    fail over to, point DataTray at the saved connections for the instances involved, and it shows the exact
    plan — every statement and the instance it runs on — before anything runs. Which plan you get follows the
    group's cluster type:

    • WSFC: one statement on the target. A plain FAILOVER when the target is synchronous and every
      database is failover-ready; otherwise FORCE_FAILOVER_ALLOW_DATA_LOSS, with a red warning, how far
      behind each database is, and what to do about the old primary afterwards.
    • Read-scale (CLUSTER_TYPE = NONE): the documented sequence across both instances — make both
      replicas synchronous, wait until the target is SYNCHRONIZED, take the group offline on the primary,
      promote the target, demote and resume the old primary, re-create the listener. It stops before taking
      the group offline if the target never catches up.
    • Pacemaker (CLUSTER_TYPE = EXTERNAL): DataTray refuses, because the cluster manager owns the
      primary role, and shows the pcs/crm commands with the target node filled in to run yourself.

    A forced or read-scale failover asks you to type the group name. Each picked connection is checked to
    really be the replica it was picked for, and when you confirm, the state is read again: if the plan
    changed in the meantime (a target that fell behind turns a planned failover into a forced one), nothing
    runs. Failing over is not reachable from the MCP server.

  • New availability groups can be created from the Availability Groups folder: New Availability
    Group…
    .
    The instance you opened it on becomes the primary; tick the saved connections that should hold
    the secondaries. A pre-flight over all of them comes first, and while anything blocks — one instance
    only, Always On switched off, different versions or collations, an edition without availability groups,
    a login without CONTROL SERVER, endpoints on only some instances — it shows only why, and no form. After
    that the form offers only what can work on those instances: WSFC only when every instance is a node of the
    same Windows cluster, read-scale (NONE) never preselected because it is not high availability, a basic
    group on Standard edition, and only the databases that can join (the others are listed with the reason).
    DataTray creates certificate-authenticated endpoints and exchanges the public certificates between the
    instances itself, without writing a file anywhere, or reuses the endpoints if every instance already has
    one. The databases are seeded automatically. As with failing over, the whole plan is shown per instance
    before anything runs, and it is checked again when you confirm.

  • Plugin releases are published by the build pipeline. Bumping a plugin's version now builds it,
    packages it and puts it in the Plugin Store on its own, so a new plugin version reaches the store the
    day it is finished instead of waiting for someone to build and upload it by hand. Store versions
    carry a build number (0.8.0.41) identifying the exact build a plugin came from.

  • The query editor and result grid can now be resized by dragging the splitter between them —
    previously they held a fixed 2:3 height ratio. The chosen height is remembered across restarts, the
    same way the resizable bottom tool panels (Output, Containers, AI activity) already are.

  • SQL Server's Administration folder gets an Availability Groups entry, next to Agent Jobs. It is
    badged disabled when Always On is switched off on the instance, and absent entirely on an
    edition/platform with no Always On support at all (Azure SQL Database, for instance).

  • An availability group now opens the same read-only dashboard SSMS shows: group info (cluster type,
    quorum, listener, backup preference), a replica table, and a per-replica database table with a derived
    "behind by" column — the primary's last commit time minus the replica's, in seconds, next to the DMVs'
    own log-send/redo queue sizes in kilobytes. It is the only node dialog in DataTray that polls (every 10
    seconds): queue depth moves while you are looking at it, unlike everything else this dialog family shows.
    Failing a group over is its own action on the group (Fail Over…), and creating one is New
    Availability Group…
    on the folder.

  • Filter the connection tree from the sidebar. A field under Connections narrows the tree while
    you type: connection names when everything is collapsed, and schema/table/view/column names inside
    whatever you have expanded. Non-matching rows are hidden rather than greyed out, the path down to a
    hit stays visible so you can see where it lives, and a footer line says how many of the loaded
    objects matched. Esc clears it and Ctrl/Cmd+F puts the caret in it (rebindable, under
    Settings ▸ Keyboard). It never expands a branch by itself — what you have not opened has not been
    fetched, and is therefore not searched. This is the counterpart to Ctrl/Cmd+K, which jumps to
    one object and closes again; the filter stays put.

  • Text in a single-line input sits centred again. Every TextBox is a fixed 32px tall, but its
    content was anchored to the top, so the slack piled up underneath and the text read as sitting high —
    worst in the new sidebar filter, visible everywhere else. Multi-line boxes (SQL previews, cell values)
    keep their first line at the top, where it belongs.

  • The filter shows which part of a name it matched, highlighted in the row, and the filter box keeps
    an accent ring while it is narrowing the tree so a partial tree never looks like the whole one. The
    search glyph and the clear cross now sit inside the field.

  • You choose where DataTray keeps your connection passwords. Onboarding has a third step, between
    picking an engine and adding your first connection: the system vault your OS already runs (macOS
    Keychain, Windows Credential Manager, Linux Secret Service) or an encrypted file in your DataTray
    profile. Both options say who holds the key, who else can reach it and what you lose if it goes wrong,
    so the choice is made on the trade-off rather than on which sounded safer.

  • The encrypted file store works where there is no keychain at all. A headless or locked-down Linux
    box has no Secret Service, and until now that meant DataTray could not save a password there at all —
    it fell over at startup. That machine now gets the file store, with the vault option greyed out and the
    reason spelled out. The file is AES-256-GCM under a master password you set in the same step; DataTray
    never writes a secret into it without one.

  • Preferences ▸ Security says which store you are on. And with the file store active, "Disable" for
    the master password is gone — the store cannot work without it — replaced by the sentence that says so.
    Existing installations are on the system vault, exactly as before, and nothing moves on its own.

  • DataTray tells you what it is doing while it starts. A small window shows the real startup steps
    (applying staged plugin updates, loading your plugins, putting your workspace back, starting
    extensions) as rows filling a tray. A step that takes longer than five seconds says so, how long it has
    waited and why DataTray needs it; after thirty seconds on your plugins you can start without the ones
    from the Plugin Store. If a step fails you see the error and can retry, open the log, continue with the
    built-in engines or quit, instead of the app closing without a window. The splash follows your theme,
    shrinks to a compact layout on small screens and after a restart, and holds still when your system asks
    for reduced motion.

  • Plugins can now add a pane to query tabs, read the connection's tables and columns, and link the editor (host API 9). Plugins can also add items to table/view context menus.

  • Drag a table or view from the tree into the query editor to insert its qualified name at the drop point.

  • Extension plugins can contribute settings and shortcuts, and uninstalling a plugin now asks for confirmation first.

  • Long queries show what the server is saying, while it says it. A query tab gets a Messages tab
    next to its results as soon as a run has something to report: PRINT and RAISERROR (also
    WITH NOWAIT, line by line as the script runs) and (n rows affected) per statement on SQL Server,
    NOTICE/WARNING on PostgreSQL, and warnings on MySQL. Every line has its time; warnings and errors
    are marked and counted, and an error that stops the run sits in the same timeline as the messages
    before it. Filter by text or level, copy the selection or what is shown, clear it, and the list follows
    the newest line until you scroll up. It keeps the latest 10,000 lines and says when older ones were
    dropped. While a query runs, Run becomes Stop with a ticking clock beside it, and the status bar shows
    the latest message; afterwards it says whether the run completed, was cancelled or failed, and where.
    Messages are cleared when the next run starts, or kept behind a divider with
    Settings › Query › Keep messages between runs. Engines without messages show only the clock.

  • Prometheus provider (PromQL, read-only). Connect to a Prometheus-compatible endpoint and query
    it in PromQL from a normal query tab. The tree browses metrics (with their type and help text) and
    their labels; instant queries, range selectors (up[1h]) and subqueries all come back as a grid of
    <labels…>, timestamp, value. Read-only by nature — the HTTP API accepts no writes, so nothing in
    the grid or the DDL menus pretends otherwise. Debug-staged like the other plugins/ providers.

Changed

  • SSH.NET updated to 2026.0.0. The library behind SSH tunnels was on a version carrying a known
    vulnerability ([GHSA-q939-rpr3-3284](htt...
Read more

Preview build (main)

Preview build (main) Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Nov 14:33
d8d4ef2

Added

  • Plugin releases are published by the build pipeline. Bumping a plugin's version now builds it,
    packages it and puts it in the Plugin Store on its own, so a new plugin version reaches the store the
    day it is finished instead of waiting for someone to build and upload it by hand. Store versions
    carry a build number (0.8.0.41) identifying the exact build a plugin came from.
  • Prometheus provider (PromQL, read-only). Connect to a Prometheus-compatible endpoint and query
    it in PromQL from a normal query tab. The tree browses metrics (with their type and help text) and
    their labels; instant queries, range selectors (up[1h]) and subqueries all come back as a grid of
    <labels…>, timestamp, value. Read-only by nature — the HTTP API accepts no writes, so nothing in
    the grid or the DDL menus pretends otherwise. Debug-staged like the other plugins/ providers.

Changed

  • SSH.NET updated to 2026.0.0. The library behind SSH tunnels was on a version carrying a known
    vulnerability (GHSA-q939-rpr3-3284), which made every
    build report it. The flaw is in SCP file transfer — an API DataTray does not use, so nothing was ever
    exposed through it; this is about not sitting on a vulnerable version. Tunnels behave as before: password
    and private-key authentication, host-key fingerprint checking, and the forwarded local port are unchanged.

Fixed

  • The macOS application menu says "About DataTray" again. It still carried Avalonia's own
    fallback item, so the first entry under the Apple logo read "About Avalonia" and opened the
    framework's about box instead of DataTray's.
  • "What's new" now actually shows what's new, and the Updates settings can start the download. The
    release notes were never put into the update packages, so the dialog opened empty on every channel —
    stable included. They are now rendered once per build and embedded, so the notes on the release page
    and the ones the app shows are the same text. The Updates pane in Settings also gained a Download
    Now
    button beside What's new, with the progress and the install step alongside it, so an update
    can be taken without closing Settings to reach the banner.
  • A query tab opened from the tree now starts on that node's database. "Select top 1000", the
    SQL command templates and "INSERT (with data)" opened their tab on the connection's default database
    (master) instead of the one the table lives in — visible in the database picker, and a real failure
    on engines that cannot reach across databases. New Query, reopening a file, duplicating a tab and
    Ctrl+Shift+T keep the database too, and switching a tab's connection no longer drops it while the
    new database list loads.
  • The setup wizard's "Install…" now opens the Plugin Store on the engine you clicked. Every tile
    under "From the Plugin Store" opened the store on whichever plugin its own list happened to show
    first, so clicking ClickHouse could land you on DragonflyDB.
  • Restarting from the Plugin Store during setup brings the wizard back. The store's own "Restart
    now" ended onboarding on the way down, so an engine installed there left you with no wizard, no
    connection and no sign of what had been installed. The wizard now returns to the engine step and
    says which engine landed.
  • Typing a schema before the dot now narrows the completion list to that schema. SELECT * FROM [dbo]. offered every table in every schema — and FROM dbo. without brackets offered every
    column of every table, because the schema name was read as a table alias that resolved to
    nothing. A dot in FROM/JOIN is now understood as a schema qualifier, and [dbo], `dbo`,
    "dbo" and bare dbo are all read the same way.
  • The tree's context menu no longer acts on the previously selected node. Right-clicking the empty
    space below the last row left the old selection standing and opened the menu against it — so
    Drop Schema… could be confirmed for a schema you never clicked. A click that hits no node now
    clears the selection and opens no menu.
  • Drop and Alter dialogs name the database they will run against. The confirmation used to show a
    bare DataSync, while DROP SCHEMA [DataSync] names no catalog of its own; it now reads
    rick-test › DataSync, so which database is about to lose the schema is visible before you confirm.

These builds are unsigned / not notarized.
macOS: after moving to /Applications, clear quarantine: xattr -cr "/Applications/DataTray.app".
Windows: pick the -Setup.exe (per-user, no admin) or the -Portable.zip; SmartScreen may warn on first launch.

DataTray 0.8.0

Choose a tag to compare

@github-actions github-actions released this 16 Aug 18:26
16b6d40

Added

  • A plugin can open its own tab. Until now a tool plugin got a dialog: collect input, run, report,
    close. That is the wrong container for anything you want to keep open while working — so a tool may now
    open as a tab in the main window instead, beside your query tabs, with its own content, title and icon.
    Reopening the same tool on the same target brings you back to the tab you already have rather than
    stacking another. Nothing changes for existing tools. The first plugin to use it will be the ER diagram.
  • Bring your connections over from DataGrip or DBeaver instead of retyping them. The Connection Manager
    toolbar has a new import button: it scans the places both clients keep their config — every installed
    JetBrains IDE's dataSources.xml, every DBeaver workspace's data-sources.json — and shows what it found
    with a tick box per connection. Host, port, database, user and DBeaver's folder come along; the engine is
    read from the JDBC URL, so PostgreSQL, MySQL/MariaDB, SQL Server and SQLite all land on the right provider
    with their fields filled.
  • Passwords are deliberately not imported. DataGrip keeps them in the IDE keychain and DBeaver in its own
    encrypted credentials file — both are another application's secret store, and DataTray does not read them.
    An imported connection arrives without a password and asks for it once, on first connect.
  • Anything found but not importable — an engine DataTray has no provider for, a provider whose plugin is not
    installed, an entry with no JDBC URL — is still listed with the reason, so a partial import says so rather
    than quietly skipping rows.
  • SQL Server Agent jobs can be started, stopped, enabled and disabled, the way SSMS does it from a job's
    context menu. The four actions sit straight on a job's context menu, next to Delete Job… and with New
    Job…
    on the Agent Jobs folder — no submenu in between. Nothing to fill in, so the dialog is a short
    explanation, a button and the log Agent's answer lands in. The job editor (steps, schedules,
    notifications) is not part of this.
  • The Agent Jobs folder says when the Agent service is not running, instead of looking live while every
    action on it comes back refused. A job's configuration sits in msdb whether or not Agent runs, so the jobs
    themselves still list — the folder just tells you nothing will fire.
  • The job list says what it is worth saying at a glance. A job that is switched off reads disabled, a
    job whose last run failed, retried or was cancelled carries that as a badge, and hovering any job shows
    when it last ran. A job that has never run stays unlabelled rather than being reported as failed.
  • Agent jobs have a Properties dialog. Right-click a job ▸ Properties… opens the same page-rail dialog
    Database Properties uses. General shows what the job is and lets you change it — enabled, description,
    category and owner are editable and saved back to Agent. History lists every run Agent still holds,
    job outcomes and step rows together, with the message that says why a run ended the way it did. No cap of
    our own: Agent's own retention already bounds what is there.
  • Job steps can be edited, not just read. The Steps page adds, changes, deletes and reorders a job's
    steps: name, type, the account it runs as, database, command, output file, retry attempts and interval, and
    what happens on success and on failure — including jumping to a specific step. The type list comes from the
    server rather than a fixed set, so a box without SSIS or replication does not offer them.
  • Schedules can be created, changed and removed from the Schedules page: daily, weekly, monthly on a
    day or on a relative day ("the second Friday"), one time, or tied to Agent starting or the CPUs going idle
    — each either at one moment or repeating inside a window. The page writes the sentence it is about to save
    as you build it, so "every 2 weeks on Mon, Wed, Fri, every 30 minutes between 08:00:00 and 17:00:00" is
    something you read rather than something you infer from six numeric fields. Removing a schedule detaches it
    and only deletes it when no other job still uses it.
  • Alerts, Notifications and Targets complete the dialog. Alerts creates and edits the alerts that
    respond by running the job — on an error number, an error severity, or a performance condition, optionally
    narrowed to one database and a phrase in the message. Notifications sets who Agent tells and when, per
    channel. Targets shows which servers run the job, and says so plainly when none does: a job with no
    target server is configured but will never fire.
  • Jobs can be created and deleted from the tree. New Job… on the Agent Jobs folder makes a job and
    targets it at the local server in one step, so it is not born in that never-fires state. Delete Job… on a
    job removes it with its steps and history.
  • SSIS job steps have a real editor. On the Steps page of an Agent job, picking SSIS as the type
    now replaces the command box with the fields the command is actually made of: where the package lives —
    the SSIS catalog, the file system, or either package store — the package itself, the environment to run it
    against, the logging level, the 32-bit runtime flag, and per-connection-manager overrides. Catalog packages
    are picked from a browser rather than typed, folder to project to package. The dtexec command is built
    from those fields and shown read-only, because it is a generated argument string in which every escaped
    quote matters and a hand-typed mistake only surfaces when the job runs.
  • Existing SSIS steps are read back into that editor, which matters more than the editor does: nearly
    every one of them was written by SSMS. A step whose command uses an option the editor does not model keeps
    its text box with the command untouched, and says which option that was — a dropped option would change
    what the step does without anyone touching the field. An environment reference the catalog no longer has is
    reported by id instead of quietly resetting to none, which is the most common way an SSIS step is broken
    and the one whose run-time error points nowhere.
  • The Run as list now only offers proxies that may run the selected type. A proxy is granted per
    subsystem, and offering one without the grant produced a step that failed to save or could not start. Where
    a step has no proxy the SSIS editor names the account it will actually use — the Agent service account,
    which usually has no rights on SSISDB — instead of the unhelpfully vague "(default)".
  • The connection import reaches four more clients. Alongside DataGrip and DBeaver it now also finds:
    • .pg_service.conf — libpq's connection-service file, where each [section] is a named PostgreSQL
      service.
    • MySQL Workbench — the saved connections in connections.xml.
    • Azure Data Studio and VS Code — the mssql.connections profiles in your user settings. The SQL
      Server way of writing one endpoint as host,1433, tcp:host,1433 or host\INSTANCE is split into the
      host and port fields; a named instance is dropped, since resolving it needs the SQL Browser.
    • MongoDB Compass — its saved connections, including Atlas mongodb+srv:// URIs (which carry no port
      to import, so the provider's default stands).
  • A password that the source file spells out now comes along, so you don't retype what DataTray just
    read: the password= line in .pg_service.conf, an inline user:password@host in a URI, and the
    password an editor writes when you decline its credential store. It goes straight to your OS keychain,
    the same place a hand-typed password lands, and never into the config file.
  • A password held in another application's secret store is still left alone — not the OS keychain
    entries DataGrip and MongoDB Compass use, and not DBeaver's encrypted credentials file. Those
    connections arrive without one and ask on first connect.
  • Because that differs per client, each row in the picker says whether a password is coming with it.
  • The import can now fetch the passwords DataGrip keeps in your system's credential store, so a
    DataGrip connection arrives ready to use instead of asking you to retype what it already had. Nothing is
    fetched while DataTray reads config files: the picker shows a separate "Also fetch N passwords…"
    button, and pressing it is the opt-in. Your operating system still decides — it may prompt, and it may
    refuse; both simply mean the connection comes in without a password, exactly as before.
  • Whatever comes back goes straight into DataTray's own keychain, the same place a hand-typed password
    lands, and never into a config file.
  • DBeaver is deliberately still left alone. Its passwords are sealed with a key that ships inside
    DBeaver itself rather than held by your operating system, so nothing there is asked on your behalf —
    which is the whole basis on which reading another client's passwords is reasonable.
  • A first launch now welcomes you instead of leaving you with a tray icon. A four-step wizard —
    welcome, engine, connection, done — runs once on a fresh profile and never again. Skip is on every step,
    and skipping counts as an answer: it won't ask again.
  • Choosing an engine is where the plugin model is introduced, because it's where it answers a question
    you're already asking. The four included engines sit above the ones the Plugin Store offers, and picking
    one of those opens the store to install it.
  • Plugins load when DataTray starts, so an engine installed during onboarding needs a restart before you
    can connect with it. The wizard says so, restarts, and comes back to the step and engine you were on
    rather than starting over.
  • The wizard offers to take over your existing connections the moment you reach the engine step —
    any...
Read more

Stable channel manifest (pre-Velopack updater)

Choose a tag to compare

@github-actions github-actions released this 16 Aug 18:26
16b6d40

Update manifest read by the pre-Velopack in-app updater. It points at the frozen legacy-stable release, which is the build that carries those installs across.

Transition build for the stable channel

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Aug 18:25
16b6d40

Frozen on purpose. The pre-Velopack in-app updater is pointed here, so installs still on the old update method can reach a Velopack build. Never delete this release or its assets.

Transition build for the preview channel

Choose a tag to compare

@github-actions github-actions released this 16 Aug 18:25
16b6d40

Frozen on purpose. The pre-Velopack in-app updater is pointed here, so installs still on the old update method can reach a Velopack build. Never delete this release or its assets.

Transition build for the nightly channel

Choose a tag to compare

@github-actions github-actions released this 14 Aug 08:21
d0bb6c0

Frozen on purpose. The pre-Velopack in-app updater is pointed here, so installs still on the old update method can reach a Velopack build. Never delete this release or its assets.

DataTray 0.7.0

Choose a tag to compare

@github-actions github-actions released this 29 Jul 23:25
bea7201

Added

  • DuckDB is a supported engine. A store-only provider plugin — install it from Tools › Plugin Store; it
    is not bundled with the app. It opens a .duckdb file, or an in-memory database (under Advanced) when you
    only want a scratchpad, and puts its schemas, tables, views, sequences, columns and indexes in the tree,
    with row counts and column counts on the nodes. Queries, scripts, EXPLAIN, View Definition, and DDL
    Create for schemas and tables work as they do for the other SQL engines. The download is ~82 MB: DuckDB is
    an embedded engine, so the plugin carries the engine itself for every platform DataTray runs on.
  • A query can read a file directly, which is the reason to reach for DuckDB in the first place:
    SELECT * FROM 'events.parquet', read_csv_auto('data.csv') and read_json_auto(…) all just work in a
    query tab, against an in-memory connection with no database file at all. Such a result set is read-only —
    there is no table behind it to write to.
  • Editing works for a plain browse. DuckDB's driver does not tell us which table a result set came from,
    so the provider works it out from the query itself: double-click a table, filter it, sort it or page
    through it and the grid stays editable, provided the table has a primary key and the query still selects
    it. Anything more — a join, an aggregate, a view, a file — comes back read-only rather than risking a save
    against the wrong rows.
  • Cancelling a long query genuinely stops it. DuckDB is an analytics engine, so a query that runs for a
    minute is normal rather than a mistake, and its driver ignores the usual cancellation signal; the provider
    bridges that so the Cancel button does what it says.
  • ClickHouse is a supported engine. A store-only provider plugin — install it from Tools › Plugin
    Store
    ; it is not bundled with the app. It connects over ClickHouse's HTTP interface
    (port 8123, or 8443 with the protocol set to https for ClickHouse Cloud) and puts its databases, tables,
    views, columns and data-skipping indexes in the schema tree, with on-disk sizes and row counts on the
    nodes. Queries, scripts, EXPLAIN, the database switcher, View Definition, DDL Create for databases and
    tables, the Activity Monitor and user/role management all work as they do for the other SQL engines. Spin
    a local server up from the Local Containers plugin like any other engine — the provider ships its own
    container recipe.
  • Three things follow from ClickHouse being columnar rather than row-oriented, and are worth knowing rather
    than discovering: result grids are read-only (the HTTP protocol carries no primary-key metadata to
    trace a result back to one table, and ClickHouse edits rows through asynchronous ALTER TABLE … UPDATE
    mutations, which a generated UPDATE … WHERE key = … would not express); a multi-statement script is sent
    one statement per request, because the server rejects a batched body outright; and a batch is not
    transactional
    , since ClickHouse has no transaction for ordinary MergeTree work — a failure leaves the
    statements before it applied.
  • Generated CREATE TABLE DDL declares ENGINE = MergeTree with an ORDER BY over the columns marked as
    primary key (tuple() when none are), and expresses a nullable column as Nullable(T) — ClickHouse
    columns are NOT NULL unless the type says otherwise, the opposite of every other engine here.

Changed

  • Containers DataTray starts are now labelled kontena.source=datatray, not sqlexplorer. The
    Kontena desktop app shows them under the new name; containers created before this release keep the
    old label and are still recognised. Anything else filtering on the old value needs updating.

These builds are unsigned / not notarized.
macOS: after moving to /Applications, clear quarantine: xattr -cr "/Applications/DataTray.app".
Windows: pick the -setup.exe (per-user, no admin) or the .zip; SmartScreen may warn on first launch.

DataTray 0.6.1

Choose a tag to compare

@github-actions github-actions released this 27 Jul 18:49
e7f9ff4

Changed

  • Downloads are named DataTray-<version>-… instead of LionearDataTray-<version>-…. The prefix
    repeated something the download URL already says, and it read as part of the product name. The
    installer, the portable zip, the AppImage and the DMG all lose it. Releases published before this
    keep the filenames they shipped with, and the in-app updater is unaffected — it resolves builds
    through the release manifest, not by guessing a filename.

These builds are unsigned / not notarized.
macOS: after moving to /Applications, clear quarantine: xattr -cr "/Applications/DataTray.app".
Windows: pick the -setup.exe (per-user, no admin) or the .zip; SmartScreen may warn on first launch.

DataTray 0.6.0

Choose a tag to compare

@github-actions github-actions released this 27 Jul 18:27
2a5354f

Added

  • Connections can reach a database through an SSH tunnel. A database that only listens inside a private
    network no longer needs a hand-rolled ssh -L next to DataTray: switch on Connect through an SSH
    tunnel
    under Advanced, fill in the bastion's host, user and either a password or a private key, and the
    connection is forwarded through it. The tunnel opens on first use, is shared by every connection taking the
    same route, and closes when you disconnect or quit. Test does the same thing, so a tunnel can be checked
    before the connection is saved.
  • SSH passwords and key passphrases are stored in the OS keychain like every other connection secret, never
    in the connection file. Filling in the server's SHA256 host-key fingerprint pins it — a bastion presenting
    a different key is then refused instead of trusted.
  • The section only appears for engines that connect to a host, and needs nothing from the provider: existing
    provider plugins gained tunnelling without a change or a rebuild.
  • The result grid's cell editor now matches the column's type. A boolean column edits as a checkbox
    and a date column as a date picker, instead of typing true or a date as text and hoping it parses. A
    column that accepts NULL gets a three-state checkbox, so clearing it is still a NULL rather than a
    false; a date cell can be cleared back to NULL the same way. Picking a date keeps the cell's existing
    time of day, so editing the date half of a timestamp no longer drops the time. Every other column type
    keeps the text editor it had.
  • Star a query to keep it. Every row in the History panel has a star; starred queries are kept in
    their own store, so they stay in the list after Clear history and when the history rolls over — a row
    that history no longer holds simply shows no row count or duration, and still opens in a query tab on
    double-click. The star in the panel header narrows the list to starred queries only.
  • Star a connection to keep it within reach. Right-click a connection → Add to favorites, and it
    appears in a Favorites section pinned to the top of the sidebar, whatever folder it lives in. By default
    it stays visible in its own folder as well — the section is a shortcut list. Settings → General → Keep
    favorites in their folder too
    turns that off, and a starred connection then moves to Favorites instead
    of being shown twice. Temporary connections (created by an AI client over MCP) can't be starred, since
    they don't outlive the session.

Changed

  • The date editor's calendar now follows the app's own theme. The day grid, the month header and the
    navigation arrows used to come straight from the Fluent theme, so the panel around them matched the rest
    of the app while the calendar inside it did not. Day cells, hover and the month header now use the app's
    colours, the selected day is a filled accent cell instead of a thin blue ring, and today is marked with
    accent-coloured text rather than a solid block that competed with the selection.
  • The flyout is also noticeably smaller: Fluent sizes a calendar for fingertips, which in a grid cell's
    popup dwarfed everything around it.
  • SQL Explorer is now called DataTray. Same application, new name — the window title, the tray tooltip,
    the About dialog, the plugin contract and the published downloads all say DataTray, and the macOS bundle
    is DataTray.app. Upgrading over an existing SQL Explorer install replaces it in place rather than
    leaving a second copy behind.
  • Your settings move to the DataTray folder by themselves. On first start after the rename, DataTray
    copies the old SQL Explorer folder — connections, query history, favourites, keymap, open tabs and
    installed plugins — to its own. Saved passwords move too, the first time each connection needs one.
  • The old folder is left where it is rather than deleted, so an older SQL Explorer build still starts with
    everything intact. It gets a MOVED-TO-DATATRAY.txt note pointing at the folder that is now live. The
    two stop tracking each other from that point on, so changes made in DataTray won't show up in the old
    build — delete the old folder once you're sure you won't go back.
  • New application icon. DataTray now carries its own mark — a database cylinder with a puzzle piece —
    in the window, the tray, the taskbar, the About dialog and the installers, replacing the one it inherited
    from SQL Explorer.

Fixed

  • A NULL cell no longer turns into an empty string just because you passed through its editor. In the
    editable grid, opening a NULL cell and leaving it without typing could write an empty string back — on a
    text column that is a real change, and it saved as '' instead of leaving the NULL. Empty text over a
    NULL cell now leaves the NULL alone; Set empty in the cell's right-click menu writes an empty string
    deliberately, next to the existing Set NULL.
  • Adding a row now writes a NULL you asked for. Columns you leave untouched are still left to the
    database, so defaults and auto-increment keys work as before — but a cell you explicitly set to NULL is
    written as NULL, where it used to be dropped from the INSERT and silently replaced by the column's
    default.

These builds are unsigned / not notarized.
macOS: after moving to /Applications, clear quarantine: xattr -cr "/Applications/DataTray.app".
Windows: pick the -setup.exe (per-user, no admin) or the .zip; SmartScreen may warn on first launch.