[h2] Re: Req: make FROM optional in DELETE statement

My bad, DISTINCT... ORDER BY UPPER works indeed as one can test using set mode regular; with a as (select 'a', 'b') select distinct 1 from a order by upper(2) As to the mode, I understand it's confusing. I am at the mercy of that legacy app which sends non-standard SQL except if it the driver id

[h2] Re: Req: make FROM optional in DELETE statement

9 at 5:04:27 PM UTC-4, Yan wrote: > > I have a 3rd-party application that supports Oracle and I wanted to test > it with h2. > It errors out on DELETE WHERE ... because H2 requires the FROM > keyword. Weird construction as I didn't know but Oracle, MSSQL and maybe > other

[h2] Req: make FROM optional in DELETE statement

I have a 3rd-party application that supports Oracle and I wanted to test it with h2. It errors out on DELETE WHERE ... because H2 requires the FROM keyword. Weird construction as I didn't know but Oracle, MSSQL and maybe others have the FROM as optional. Hence the request to make it optional

[h2] Re: cache size vs. disk size

Thanks Andrei. Not sure though why the file would grow as it is 500MB already (.mv.db) and the front-end app does not update, insert or sends DDL. It is pretty much read-only, except one or 2 small tables updated for stats purposes. Are you saying deserialized data take up much more space ? I w

[h2] cache size vs. disk size

I have a db that on the file system takes 500MB that would barely grow. If I want to maximize the use of cache (that is, keep in memory at first read), what should be the optimal size of it ? 500MB (rounded to 512MB in case of overhead), more, or less ? I am not sure space on disk equates spac

[h2] Re: Next release date?

Same question - it's been 9 months and close to 1800 commits since 1.4.197. We don't mind building the artifact but would rather see an official release update. Thanks. On Wednesday, September 12, 2018 at 4:50:43 AM UTC-4, Göran Schwarz wrote: > > Hi there! > > Do you have an idea when next vers

[h2] Re: Read environment variables in script

e script through the java command-line. On Monday, May 29, 2017 at 12:03:28 PM UTC-4, Yan wrote: > > I use the following UDF to read: > > CREATE ALIAS GET_ENV AS $$ > String getEnv(String value) { > return new System.getenv(value); > } > $$; > > Can this be ad

[h2] Re: Read environment variables in script

typo - removed "new". Working code: > CREATE ALIAS GET_ENV AS $$ > String getEnv(String value) { > return System.getenv(value); > } > $$; > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emai

[h2] Read environment variables in script

I use the following UDF to read: CREATE ALIAS GET_ENV AS $$ String getEnv(String value) { return new System.getenv(value); } $$; Can this be added as a new system function into core H2 ? This is useful in combination of CSVREAD/CSVWRITE in case the path to the file is defined in an environm

Re: [h2] Re: Voting up for SQL Trigger

Thanks Noel - any target release and ETA for it ? On Wednesday, January 18, 2017 at 11:29:38 PM UTC-5, Noel Grandin wrote: > > I'd be happy with a patch that did that > On Tue, 17 Jan 2017 at 22:47, Yan > > wrote: > >> Fair enough Noel. >> >> What about

Re: [h2] Last chance SQL editing in JDBC + fooling DBProduct name

va.sql.Connection class which does the > regex mangling you describe, prior to passing the SQL off to the real JDBC > Driver's Connection object. > > It would have the advantage of being able to work with any JDBC driver and > so be potentially useful to users of non-H2 d

[h2] unnecessary properties entries when using URL_MAP

H2 creates internal db management urls in the properties file when using URL_MAP e.g. jdbc\:h2\:mem\:management_db_55769= It does not affect functionality but is unnecessary and not reusable. Can you filter these out in the next release ? -- You received this message because you are subscribed

[h2] Last chance SQL editing in JDBC + fooling DBProduct name

Despite all the built-in flexibility of H2 to be compatible with other databases, there are instances where apps are designed - and one has no access to the source code - to work only with specific RDBMS, say Oracle or MSSQL. I still want to use h2 for development instances and not go through t

Re: [h2] Re: Voting up for SQL Trigger

Fair enough Noel. What about opening up inline java coding like alias/functions ? Currently triggers must refer to an existing compiled class - the alternative to provide the java code in the trigger creation statement would really be a plus. As an alias gets implicitly the connection, a tri

[h2] Re: Voting up for SQL Trigger

H2 too ? Thanks, Yan On Monday, February 4, 2013 at 6:54:09 PM UTC-5, Thomas Mueller Graf wrote: > > Hi, > > Of course one option would be to provide a patch for H2 :-) > > About compatibility: should H2 support T-SQL (Microsoft), PL/SQL (Oracle), > or another? See also >

Bug on H2 service installation batch file "1_install_service.bat"

A bug exists on the H2 service installation batch file "1_install_service.bat" at line 6: The jump label "start" doesn't exist. @echo off setlocal copy /y /b ..\bin\h2-*.jar ..\bin\h2.jar fc /b ..\bin\h2-*.jar ..\bin\h2.jar if not errorlevel 1 goto :start <-- labe