Sorry about this. Actually no, it's not working. I just created a new blank database apparently in a new directory. Still having the original problem trying to open the DB in HSQL GUI. Any ideas?
- Dave On Sun, Apr 23, 2017 at 2:23 PM, David Kincaid <kincaid.d...@gmail.com> wrote: > I got it figured out. I was using the wrong URL path for the database. > Working great now! > > - Dave > > On Sun, Apr 23, 2017 at 12:31 PM, David Kincaid <kincaid.d...@gmail.com> > wrote: > >> Thanks for the reply, James. I'm not very familiar with HSQLDB, so I may >> be doing it wrong, but I launched the GUI using "java >> -jar hsqldb-2.3.4.jar" and then tried to connect to the DB by changing the >> "Type" to "HSQL Database Engine Standalone" and then setting the URL to >> point to my custom dictionary directory. It throws a SQLException that says >> "wrong database file version". Is there some other step I'm missing? >> >> - Dave >> >> On Sat, Apr 22, 2017 at 10:31 PM, James Masanz <masanz.ja...@gmail.com> >> wrote: >> >>> Dave, >>> >>> It's an oversight that we didn't document that. Thanks for pointing that >>> out! I'll update the documentation tomorrow and post again with proper >>> details of the command to use. >>> >>> The short answer is that hsqldb jar includes a GUI. You use the 2.3.4 >>> version of that jar, which is included with the cTAKES 4.0 convenience >>> binary, to open your database. Then you close (shutdown) your DB and it >>> gets converted to 2.3.4 for you. But if the .properties file for your DB >>> indicates it's readonly, you need to have edited the properties file >>> first >>> to remove that. That gives you the idea. I'll write it up properly >>> tomorrow. >>> >>> Thanks for testing, >>> -- James >>> >>> >>> *Sent from my phone.* >>> >>> On Apr 22, 2017 9:39 PM, "David Kincaid" <kincaid.d...@gmail.com> wrote: >>> >>> I finally had some time this weekend to give 4.0.0rc3 a run. The install >>> and configuration instructions worked perfectly on my Linux laptop and I >>> was able to use CVD to run the clinical pipeline successfully against >>> some >>> of the clinical notes I have here. >>> >>> However, I ran into a problem when I tried running my own customized >>> pipeline that includes a custom dictionary that I create (to include the >>> SNOMED veterinary extension). I get an exception while it's loading that >>> the dictionary is not the correct version. So, I assume I just need to >>> recreate that custom database? Or is there a migration utility from the >>> old >>> database version to the new version? >>> >>> I don't remember seeing mention of this, but certainly could have missed >>> it. If it's not in the release notes or install/upgrade instructions it >>> probably should be there. >>> >>> Thanks to everyone for pulling this release together and getting it out >>> the >>> door! >>> >>> - Dave >>> >> >> >
