I think the solution to add following to .psqlrc is far from perfection \set ON_ERROR_STOP on there exists much more simple and convenient way – use psql with parameter: psql -v ON_ERROR_STOP=1 better to use also -X parameter turning off .psqlrc file usage. Works perfectly for me p.s. the solution found in great post from … Read more
As documented under Data Type Default Values: If the column can take NULL as a value, the column is defined with an explicit DEFAULT NULL clause. (I think they meant implicit, not explicit). Moreover, as documented under CREATE TABLE Syntax: If neither NULL nor NOT NULL is specified, the column is treated as though NULL … Read more
By default, Spring-Boot loads data.sql and/or data-${platform}.sql. However, keep in mind that the script would be loaded at every start, so I would think it makes more sense (at least for production), to just have the values already present in the database, not re-inserted at every start. I’ve personally only used database initialization for test/dev … Read more
If your filename is myQueries.sql, just type SQL>@/path/to/my/query/myQueries.sql SQL>/
There is great way of executing SQL scripts from Java without reading them yourself as long as you don’t mind having a dependency on Ant. In my opinion such a dependency is very well justified in your case. Here is sample code, where SQLExec class lives in ant.jar: private void executeSql(String sqlFilePath) { final class … Read more
You’re looking for USER_TAB_COLUMNS – all the columns, and their descriptions in the schema the query is executed in – or ALL_TAB_COLUMNS – the same except for all tables that user has permission to view. A typical query might be: select * from user_tab_columns where table_name=”MY_TABLE” order by column_id column_id is the “order” of the … Read more
An alternate solution could be to alter the flow of execution of your script by using the GOTO statement… DECLARE @RunScript bit; SET @RunScript = 0; IF @RunScript != 1 BEGIN RAISERROR (‘Raise Error does not stop processing, so we will call GOTO to skip over the script’, 1, 1); GOTO Skipper — This will … Read more
use the sqlcmd tool to execute the file.. sqlcmd -S myServer\instanceName -i C:\myScript.sql In case your have an unexplained “script error” for large sql files (> 100MB) which includes several INSERT, just replace “INSERT INTO” by “GO INSERT INTO” in your file, which will reduce size of transaction.
You can use the RUNSCRIPT SQL statement: RUNSCRIPT FROM ‘test.sql’ or you can use the RunScript standalone / command line tool: java -cp h2*.jar org.h2.tools.RunScript -url jdbc:h2:~/test -script test.sql You can also use the RunScript tool within an application: RunScript.execute(conn, new FileReader(“test.sql”));