I am using hsqldb for junits on springn jdbc project and url is
jdbc:hsqldb:file:${basedir}/src/test/resources/hsqldb/test.db;sql.syntax_db2=true.
Even though passing sql.syntax_db2=true, SET DATABASE SQL SYNTAX DB2 FALSE statement has been creating on persistant file.So I need to make SET DATABASE SQL SYNTAX DB2 TRUE
Could pleas help on the same.
Thanks,
Raj
The DB2 syntax compatibility is turned on internally but it is not peristed in the .script file due to a bug. The workaround is to enable ORACLE syntax compatibility as well, then both get persisted.
This bug will be fixed in HSQLDB version 2.3.3.
Related
I'm getting a provision error when using PostgreSQL JDBC on GraphDB. Actually, I created a connection between postgresql and Graphdb by a virtual repository, and I made a ODBC file which includes the RDF mapping information.
Expected: Normaly I can browse PostgreSQL data's hierarchy and so on in GraphDB.
Error: The connection was fine and the repository was created successfully, but when I tried to browse the data, I got this error:
Actions that I did: I did go /opt/graphdb-free/app/lib/plugins/dependencies-plugin/dependencies-plugin.jar to modify the dependency parameter, but it didn't change anything. I did checked the syntax of ODBC file and I don't see anything wrong there.
Anyone have been though this? Was I in the right place to modify the dependency? Or it's something else?
I am going to make a db migration file and migrate the file to database by using the a command.
But I can't find the command.
In Laravel we approach the goal by using this command.
php artisan make:migrate migration_client_table
Is there any similiar command that acts like the php artisan make:migrate command?
Coming from Laravel/Symfony background as well, I was asking this myself. Here are my findings:
Laminas uses laminad-db module for interactions with database. Documentation for this module however does not mention migrations at all.
Database and Models introduction to Laminas uses sql file to create a table and fill it with some original seed and does not mention altering tables at all.
Therefore I made assumption Laminas does not handle migrations at all.
Edit: According to this answer, we can use sqitch, doctrine/migrations or liquibase
I use the snowflake driver for SQLTools on vscode and i'm connect to my snowflake account but i'm some issues when i want to put some files with extensions .csv from my local machine to my stage in snowflake. Indeed, when i use the command put file:///mypath/file.csv #nameofmystage; it works on terminal but not in the window vscode with extension Snowflake driver. However, others commands like copy into works on the driver vscode ...
The error's message is Unsupported feature 'unsupported_requested_format:snowflake'
thanks in advance for your help
Not a solution or final answer, but a hint - here someone is having the same error, but with the Go-Driver: https://github.com/snowflakedb/gosnowflake/issues/227
Go didn't support PUT in this case.
Based on the PUT documentation, currently PUT is not supported in .NET driver.
Snowflake Driver for SQLTools does not look like a driver from Snowflake, as it was not mentioned here:
Connectors & Drivers
I am not sure how the driver is built, but given both vscode and .NET are both MS product, I assume that it is not supported, but hope others can help to verify.
When I tried to copy paste the tables from my connection database and paste the tables into my local database in postgres I'm getting this error. I've been using navicat version 12 and postgres version 11. Is there any conflict in terms of versioning between the two extension?
Some resources says: p.proisagg should change into p.prokind: the question is how can I change this? I've been using windows.It would be great if anybody could figure out where I am doing something wrong. thank you so much in advance.
The software version(navicat version 12) is inconsistent with the PGSQL version(postgres version 11). As a result, some configurations are not associated. You can upgrade the software version to resolve the problem,like navicat 15 or final (now is 16).
I'm using the very latest version of Visual Studio Professional 2017 (v15.9.9) with the latest SQL Server Data Tools (v15.1.61903.01040)
I create a new stored procedure in my database project, for example, with the following code:
create proc [dbo].[MyProc] as
select 'Test' as [TestColumn] FOR JSON AUTO
It won't compile with the errors below, and the keyword JSON is highlighted:
SQL46005: Expected XML but encountered JSON instead
SQL80001: Incorrect syntax near 'JSON'
It seems strange that this doesn't compile, when it's perfectly valid SQL (or am I mistaken? Is there something I'm missing? Or is it genuinely not supported?)
This issue seemed to exist for older versions of SSDT before 2016, but was reported as resolved back then, is this perhaps a recent regression? I can't find any other instances of this error or anything like it.
If you have the "Target Platform" on the .sqlproj properties set to SQL 2014 or less or "Microsoft Azure SQL Database" then this will happen, the compatibility level doesn't affect it (or at least setting my project to 2014 compatibility didn't).
This works for me with SQL 2016+ and Azure v12 with SSDT "15.1.61902.21100"
Hope it helps!
ed