Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Cecil Westerhof Newsgroups: comp.lang.java.programmer Subject: Re: Which databases are the most used with Java Date: Sun, 13 Aug 2017 23:33:58 +0200 Organization: Decebal Computing Lines: 52 Message-ID: <87shgvqhix.fsf@munus.decebal.nl> References: <87y3qovwjb.fsf@munus.decebal.nl> <87tw1bx2c9.fsf@munus.decebal.nl> <878tins1li.fsf@munus.decebal.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="1615173a1409002a85fbdd25ac4b9ead"; logging-data="24072"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+rb49GHpgIENEoffF08lejvCfiYMmo7yw=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) Cancel-Lock: sha1:M9olrI7LE2xux+tU+XqnpH9g9vg= sha1:aNFgT45VL5TlNWxLM2cnCpiuun4= X-Homepage: http://www.decebal.nl/ Xref: csiph.com comp.lang.java.programmer:37208 Sebastian writes: > Am 13.08.2017 um 21:35 schrieb Cecil Westerhof: >> Robert Klemme writes: >> >>> Another aspect of the original question that puzzled me right from the >>> start: why does it matter at all what JDBC driver is really used. Since >>> all the types are interfaces anyway _any_ JDBC driver should work with >>> the wrapper library (except vendor specific things which require >>> specific types anyway). >> >> The only things that differs (as long as you only use generic >> functionality) is the URLPrefix. That is why I think it is not much >> work to generate the other concrete classes when the abstract and >> first concrete class are finished. >> > That's a bit optimistic. JDBC as a standard is a little vague, and I am know for being optimistic. :-D > surprising things can happen, starting with your mapping from database > types to Java SQL types (NUMERIC?, REAL?, DECIMAL?... - and this can > change even when updating from version of a driver to another of the > same vendor). Then there are the peculiarities of caching, dealing with > cursors, how to write your queries they are optimized etc. A _good_ > abstraction over JDBC has to deal with all this kind of stuff and more, > and has to keep up with changes in the databases it supports and their > official drivers. I need to be more clear again. I am making it for SQLite3. There you do not have cursors. My intention is to only use it for small applications where you only do simple work: - updating - deleting - inserting - traveling a ResultSet in one direction - … I think that when you do more as this, that you should switch to for example JPA. I will make at least also a H2 version (that is the other database I am -still- using). Maybe I should not publish it. Or if I do: with a big disclaimer. -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof