The Data Fusion Arena connects to live relational databases so you can pull records directly into the analysis grid or push your integrated dataset to a persistent store. All three supported engines use a unified workflow backed by Microsoft.Data.SqlClient (SQL Server), MySqlConnector (MariaDB), and Npgsql (PostgreSQL) — each supporting both import and export with no additional setup beyond your connection credentials.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/XxLunaxX29/ExploradorDeArchivos/llms.txt
Use this file to discover all available pages before exploring further.
Supported Databases
| Database | Driver | Default Port |
|---|---|---|
| SQL Server | Microsoft.Data.SqlClient | 1433 |
| MariaDB | MySqlConnector | 3306 |
| PostgreSQL | Npgsql | 5432 |
Importing from a Database
Open the Data Fusion Arena
Click the Data Fusion Arena button in the main toolbar to open the data management panel.
Click the import button for your database
Choose Import from SQL Server, Import from MariaDB, or Import from PostgreSQL from the database section of the toolbar.
Enter connection details
The
ShowImportDialog dialog opens. Fill in:- Server — hostname or IP address (default:
localhost) - Port — pre-filled with the default for your engine
- Database — name of the target database (default:
DataFusionArena) - Username and Password
- Windows Authentication checkbox (SQL Server only)
Select a table
The dropdown is populated by
GetTablesSqlServer, GetTablesMariaDb, or GetTablesPostgreSql depending on the engine. Select the table you want to import.Exporting to a Database
Load data in the Arena
Import or generate data within the Data Fusion Arena so the grid is populated.
Click the export button for your target database
Choose Export to SQL Server, Export to MariaDB, or Export to PostgreSQL.
Enter connection details
The
ShowExportDialog dialog opens. Fill in the server, port, database name, username, and password. You can also customise the Table name field (defaults to DatosIntegrados).Click Export
DatabaseExporter.ExportToSqlServer, ExportToMariaDb, or ExportToPostgreSql runs. The target database is created automatically if it does not exist. The table is dropped and recreated with columns discovered dynamically from the loaded data, then each row is inserted individually.DataReader Methods
The three database read methods share an identical signature. Each one first ensures the target database exists (EnsureSqlServerDatabase / EnsureMySqlDatabase / EnsurePostgreSqlDatabase), checks whether the requested table is present, and returns an empty list if it is not — so callers never need to handle missing-table exceptions.
DataItem properties by name (case-insensitive). Any column that does not match a known property is stored in DataItem.ExtraFields so no data is silently dropped.
DatabaseExporter Methods
The three export methods discover the full set of columns at runtime by inspecting everyDataItem in the list (including ExtraFields). Each column becomes a VARCHAR(500) / NVARCHAR(500) column in the target table. The return value is the number of rows inserted.