dbeaver | Free universal database tool and SQL client | SQL Database library

The issue here is with the structure of your database. Although it's valid to create a database with no primary key, this will usually cause problems, because it may force Qt to try to identify rows using a combination all their values when editing an SQL model via a view. In cases where each row does not have a unique combination of values, this is almost certain to produce unpredictable behaviour.

In your example, every row is initialised with the value 0. If that remains unchanged, deleting any row with that value will delete them all, since (as far as Qt is concerned) they all effectively have the same key.

To fix your example, you should therefore simply add a primary key, like so:

I found a solution by myself.

I just had to allow the TCP connection on wsl2(Ubuntu) and then restart postgres.

DataStax offers the JDBC driver from Magnitude (formerly Simba) to users at no cost so you should be able to use it with DBeaver.

These are the high-level steps for connecting to a Cassandra cluster with DBeaver:

1. Download the Simba JDBC driver from DataStax
2. Import the Simba JDBC driver
3. Create a new connection to your cluster

1. Go to https://downloads.datastax.com/#odbc-jdbc-drivers.
2. Select Simba JDBC Driver for Apache Cassandra.
3. Select JDBC 4.2.
4. Accept the license terms (click the checkbox).
5. Hit the blue Download button.
6. Once the download completes, unzip the downloaded file.

In DBeaver, go to the Driver Manager and import the Simba JDBC driver as follows:

1. Click the New button
2. In the Libraries tab, click the Add File button
3. Locate the directory where you unzipped the download and add the CassandraJDBC42.jar file.
4. Click the Find Class button which should identify the driver class as com.simba.cassandra.jdbc42.Driver.
5. In the Settings tab, set the following:

• Driver Name: Cassandra
• Driver Type: Generic
• Class Name: com.simba.cassandra.jdbc42.Driver
• URL Template: jdbc:cassandra://{host}[:{port}];AuthMech=1 (set authentication mechanism to 0 if your cluster doesn't have authentication enabled)
• Default Port: 9042

1. Click the OK button to save the driver.

At this point, you should see Cassandra as one of the drivers in the list.

In DBeaver, create a new database connection as follows:

1. Select Cassandra from the drivers list.
2. In the Main tab of the JDBC connection settings, set the following:

• Host: node_ip_address (this could be any node in your cluster)
• Port: 9042 (or whatever you've set as rpc_port in cassandra.yaml)
• Username: your_db_username
• Password: your_db_password

1. Click on the Test Connection button to confirm that the driver configuration is working.
2. Click on the Finish button to save the connection settings.

At this point, you should be able to browse the keyspaces and tables in your Cassandra cluster. Cheers!

Using ' and PARSE_JSON/TRY_PARSE_JSON:

First Some Background

Synapse stores all artifacts in JSON format. In the Git repo, they are in the following folder structure:

Inside each folder are the JSON files that define the artifacts. Folder sqlscript contains the JSON for SQL Scripts in the following format:

NOTE: the Synapse folder of the script is just a property - this is why all SQL Script names have to be unique across the entire workspace.

Extracting the script

The workspace does allow you to Export SQL to a .sql file:

There are drawbacks: you have to do it manually, 1 file at a time, and you cannot control the output location or SQL file name.

To pull the SQL back out of the JSON, you have to access the properties.content.query property value and save it as a .sql file. As far as I know, there is no built in feature to automatically save a Script as SQL. Simple Copy/Paste doesn't really work because of the \ns.

I think you could automate at least part of this with an Azure DevOps Pipeline (or a GitHub Action). You might need to copy the JSON file out to another location, and then have a process (Data Factory, Azure Function, Logic App, etc.) read the file and extract the query.

Found in disucssions solution to add inserts to PL/SQL block:

ShadelessFox It's not possible from a DBeaver perspective, but you can use PL/SQL blocks

Because you are comparing a date to a string, you are causing the string to be implicitly converted to a date, using your session's NLS settings. Those may be derived from your locale, or may be set explicitly by your client, e.g. through preferences.

If NLS_DATE_FORMAT is is set to 'DD/MM/YYYY' then '25/11/05' is converted to 0005-11-25, so the comparison is false. If it is set to 'DD/MM/YY' (or 'DD/MM/RR', or 'DD/MM/RRRR') then it is converted to 2005-11-25, so the comparison is true.

db<>fiddle

You should not rely on implicit conversions, or NLS settings - since you can't control the environment of whoever runs your code.

DBeaver might be using the JDBC driver to create a connection to Snowflake. You may need to pass it in the JDBC connection string at client (DBeaver) end. See- https://docs.snowflake.com/en/user-guide/security-mfa.html#using-mfa-with-jdbc

You forgot the parentheses.

The syntax for FOREIGN KEY requires them.