# Database

***

### 3.2.1

08 Apr 2026

* Fixed: Dragging and dropping text within the SQL Editor cleared the editor content

***

### 3.2.0

5 Dec 2025

* Improved: ExecuteStoredProcedure now displays a clearer error message when the stored procedure's default parameter values cause an execution error during metadata retrieval

***

### 3.1.0

27 Aug 2025

* Use the new, shared database connection editor and table chooser editor from the Sdk.UI.Database package
* Updated the Twenty57.Database package to the .NET 8.0-based version
* Updated MongoDB.Driver NuGet package
* Fixed: The horizontal scroller jumped to the right when selecting a column name in the "Objects" tab
* Fixed: DBBulkCopy threw a conversion exception when debugging
* Fixed: ExecuteSQL functions returning a Custom type reset property types when the query changed, even if output names were unchanged

***

### 3.0.5

29 Aug 2024

* Fixed: Solution fails to open with "Could not load type 'Twenty57.Linx.Plugins.Database.DbBulkCopy.Runtime.Loader
* Fixed: SQL Editor inserts invalid reference placeholder into SQL query

***

### 3.0.3

2 Aug 2024

{% hint style="warning" %}
**Important**

DBBulkCopy might lose its table mappings in solutions with more than one DBBulkCopy instance. This has been fixed, but it might happen again during the update if the solution is already affected. It will not happen again after that.
{% endhint %}

* Fixed: DBBulkCopy Table mappings are lost on load.

***

### 3.0.2

17 Jul 2024

* DbBulkCopy Table Chooser now prompts before updating the "Connection string" on save
* Fixed: Debugging a plugin using -debugPackage flag failed to resolve Microsoft.Data.SqlClient
* Fixed: Copy-pasting DBBulkCopy threw "Value cannot be null. (Parameter 'type')"

***

### 3.0.1

27 Nov 2023

* Changed the NuGet package to support multiple platforms

***

### 3.0.0

6 Jun 2023

{% hint style="warning" %}
Breaking Change

[What will break and how to fix it](/releasenotes/plugins/database/breaking-changes.md)
{% endhint %}

* Changed the plugin from Windows-specific to be platform-independent
* OLE DB has been removed as *Connection type*
* Fix bug: Expressions in SQL statement are mangled on save

***

### 2.0.0

15 Feb 2023

{% hint style="warning" %}
**Important**

In order to connect to SQL Server using aliases we had to update to the latest Microsoft.Data.SqlClient.

Please be aware that Microsoft SqlClient Data Provider for SQL Server (Microsoft.Data.SqlClient) has changed the way they handle SQL Server connections. See <https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-7.0/breaking-changes#encrypt-true> for details on what has changed and possible mitigations thereof.
{% endhint %}

* Updated to use latest Microsoft.Data.SqlClient
* Allow using SQL Server Aliases

***

### 1.3.0

28 Sep 2022

* Support for newly added Return function

***

### 1.2.0

18 Aug 2022

* Enable syntax highlighting for MySQL comments

***

### 1.1.1

23 Jun 2022

* Fix bug: Database ExecuteSQL Result Editor does not update column types

***

### 1.1.0

19 Apr 2022

* Map unknown SQL data types to string

***

### 1.0.6

13 Apr 2022

* Reduce the amount of data saved for Database functions
* Fix bug: Wrap connection error message
* Fix bug: Validation errors warning not disappearing in ExecuteStoredProcedure function

***

### 1.0.4

22 Mar 2022

* Fix bug: Cannot copy ExecuteStoredProcedure function
* Fix bug: Exception when selecting parameters in ExecuteStoredProcedure function

***

### 1.0.2

17 Mar 2022

* First release

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.linx.software/releasenotes/plugins/database.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.