Struggling with SQLite in Java console app under VSCode

The .jar needs to be part of your class path. The /src directory is generally for source code. How you add that jar to the classpath in VSCode I do not know.

You can try adding it to the CLASSPATH environment variable. I reckon it's easier to just use an IDE or to switch to another language that isn't so full of ****. Tried python? :P
 
Last edited:
Stick the .jar in the same folder as your .class files, and then in the console / terminal, navigate to that folder and run:
  • Mac / Linux: java -cp ".:*" <classname-without an extension>
  • Windows: java -cp ".;*" <classname-without an extension>
Wildcard * should capture all jar files in that folder.
Click to expand...
 
Why SQLite ? If you need an embedded db for java there better options. H2, HS, Derby to name a few. With maven and Hibernate you don’t need to care about what db is under the hood. If you want to stick with SQLite, avoid java imo.
 
zippy said:
Why SQLite ? If you need an embedded db for java there better options. H2, HS, Derby to name a few. With maven and Hibernate you don’t need to care about what db is under the hood. If you want to stick with SQLite, avoid java imo.
Click to expand...

"better options" as in easier to work with or a better DB? There's nothing difficult about SQLite and Java unless you're scared of writing SQL
 
Hamster said:
"better options" as in easier to work with or a better DB? There's nothing difficult about SQLite and Java unless you're scared of writing SQL
Click to expand...
Maybe due to full SQL92 support, e.g. SQLite doesn't support right join or full outer join.

But in return due to smaller code footprint, SQLite is smaller (but we're measuring KB here), with SQLite usually using a few MB's less than Derby.
If you want roles/schemas, Derby better.
https://www.sqlite.org/cvstrac/wiki?p=SqliteVersusDerby

I think one other major factor for Derby is built-in ability to encrypt, SQLite just has stubs for you to implement it, so is possible. One factor to take into account though is no virtual table in Derby, which again, depends on what you're trying do.

Tbh, there's no real difference between the two for most SQLite use-cases, rather go with the one you prefer using/know how.

[)roi(] said:
Why?
Click to expand...

+1
 
Hamster said:
"better options" as in easier to work with or a better DB? There's nothing difficult about SQLite and Java unless you're scared of writing SQL
Click to expand...

It’s just easier to integrate java with the other options for embedded db work.

IMO for an embedded db, spending time writing sql isnt useful.

But then the OP also chose VScode to use java, which isn’t most peoples first choice as a java ide :)
 
zippy said:
It’s just easier to integrate java with the other options for embedded db work.
Click to expand...
Huh? what exactly is so difficult about SQLite?

zippy said:
IMO for an embedded db, spending time writing sql isnt useful.
Click to expand...
Why? ...depends on the data, doesn't it.

zippy said:
But then the OP also chose VScode to use java, which isn’t most peoples first choice as a java ide :)
Click to expand...
Granted wouldn't have been my first choice, but hey all Java IDEs are laggy memory hogs anyway, so that's not a great comparison.
 
[)roi(] said:
Huh? what exactly is so difficult about SQLite?

Why? ...depends on the data, doesn't it.

Granted wouldn't have been my first choice, but hey all Java IDEs are laggy memory hogs anyway, so that's not a great comparison.
Click to expand...

I am building a small developer console for our team which will basically manage 3 local app servers and also include a file backup system for each applications local db and log files.

The system will allow a dev to start, stop the servers as well as fire up their studio ide’s.

The system will use a very simple db structure to manage the configuration parameters for the servers. The only reason I chose to use a db is the possibility of adding other servers.

I initially chose to use SQLite, then I found that I would have write all the sql and connection, I decided to use h2, because essentially I am a lazy sod and since it’s piss easy to use hibernate and I couldn’t get hibernate and SQLite to work, I chose h2.

;)

I am not afraid of sql. I was an Oracle dev for 15 years or so. Our production and QA workstream and preproduction and CI servers all run on an Oracle database and I use sql daily, but to write sql and jdbc connection code for something small is, in my view, a waste of time when there is a library that can do it for me, and the db is not an important consideration.

I’m not someone who is wedded to any particular tech. I use whatever is easier for me.

I accept someone else may feel differently and might actually prefer to write the sql. That’s fine. I’m not criticising this. I just chose to mention that I found a way that was easier for me and I’m sharing that. I won’t be offended if it’s not the route others would take :)

And OP did mention he was struggling :)
 
zippy said:
I initially chose to use SQLite, then I found that I would have write all the sql and connection,
Click to expand...
It's a just handful of statements... :rolleyes:
zippy said:
And OP did mention he was struggling :)
Click to expand...
Yes, but that was with running the Java app from the console. btw he would have experienced the same problem with any other dependency -- it certainly wasn't specific to SQLite
 
Sure :) btw, my original reason for trying SQLite was because H2 has a major weakness in that it that it only supports table level locking which when you have a app that is either multi user or you have may have a requirement for additional threads that could result in more than one thread trying to get a lock on a table, then you will be screwed. So you do need understand what your chosen embedded db can do and can’t do.
 
zippy said:
I am lazy, and like the OP’s strange attraction to VSCode, I may currently have a thing for ORM frameworks :)
Click to expand...
How exactly do you write an app with less than a handful of statements? BTW I can appreciate the OPs choice to use VScode; I too prefer the non lag performance of vi and / or Sublime Text against the sluggish memory hogs that most IDEs are.
 
[)roi(] said:
How exactly do you write an app with less than a handful of statements? BTW I can appreciate the OPs choice to use VScode; I too prefer the non lag performance of vi and / or Sublime Text against the sluggish memory hogs that most IDEs are.
Click to expand...
I use IntelliJ on Mac and windows. I don’t it find sluggish at all on either os.
 
zippy said:
I use IntelliJ on Mac and windows. I don’t it find sluggish at all on either os.
Click to expand...
Whats the specs on those machines? Will it run smoothly on a Pentium with 4GB of RAM alongside an instance of Chrome with 10+ tabs?
 
Far more likely a case of perspective; always experienced lag and being accustomed to it.
 
Also, I'd love to see you run a full on IDE on a MacBook Air :p
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X