I use H2 as my test environment (alternative to the Oracle instances
used for production) as it is almost drop-in compatible with Oracle.
I almost always use it in file mode, though. I have used it in
tcp/ip mode a few times without issue.
I never have used the run script classes.
I recommend y
This unfortunately goes way beyond my H2 knowledge. H2 is good for small tests
in embedded mode, but I never tried running it as a server.
Since you are no longer embedding it, is there a reason to use H2 to begin
with? You can run MySQL or PostgreSQL on Docker or something.
Andrus
> On Oct 2
Mike & Andrus,
Thanks for your help you got me a bit closer.
So one step forward.. but not quite there.
So, here's the path now...
In the first shell:
$ java -cp bin/h2*.jar org.h2.tools.Server -tcp -tcpAllowOthers
In a second shell
java -cp h2*.jar org.h2.tools.RunScript -url
"jdbc:h2:tcp:/
> jdbc:h2:mem:test;MVCC=TRUE
This is an in-memory DB URL. So it exists in Squirrel SQL Client process and
not on disk. Try an experiment - close and reopen Squirrel SQL Client and see
if the DB is still there.
You will need to use a URL that points to a file. E.g. jdbc:h2:/data/sample
FWIW I p
I see a couple of possible reasons:
First I would guess that "jdbc:h2:mem" is creating a separate
in-memory database rather than using your tcp-served db.
Second, you might need to specify your non-standard schemas like as follows.
Below is a url I use modified for what values you provided:
jdb
I created an H2 database, using our standard SQL. Now I'd like to
rev-engineer that db with cayenne, but the schema doesn't show up in the
modeler.
To reproduce this problem, I follow these steps:
$ java -cp bin/h2*.jar org.h2.tools.Server -tcp -tcpAllowOthers
this creates a H2 database.
I conn
