Path: csiph.com!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 11:14:28 +0200 Organization: Decebal Computing Lines: 44 Message-ID: <87pobzx217.fsf@munus.decebal.nl> References: <87y3qovwjb.fsf@munus.decebal.nl> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="1615173a1409002a85fbdd25ac4b9ead"; logging-data="22758"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18mdWpZHpRAoln2Vjru3PZg/OLePBLU784=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-Homepage: http://www.decebal.nl/ Cancel-Lock: sha1:0BiAIV0t7pP6XJi9Th2FOZw9hoc= sha1:2o8f6VwS+UshlUCL7e2ZOqOBdMg= Xref: csiph.com comp.lang.java.programmer:37167 Marcel Mueller writes: > On 13.08.17 07.58, Cecil Westerhof wrote: >> I am making a wrapper around JDBC. I myself only use SQLite3 (at the >> moment), but I want to share it. Then I should implement (at least) >> the most important databases. > > ??? - The JDBC API is common to all databases. That's the idea of it. > So what is the intention of your wrapper? Which services does it provide > to the programmer? See my reply to Sebastian. >> I should -I think- at least write an implementation for those. I am >> using Linux, but I understood that nowadays you can run SQLServer on >> Linux. So it should be doable. > > Yes, you /can/. But except for that, do you know anybody who does this > in a production environment? What should be the purpose of that? > This was just an experiment of Microsoft to be prepared for the future > (not primarily for Linux). I think a lot of Windows computers do. Java is Write Once, Run Everywhere. So if I write the implementation then someone else can use it with SQLServer without needing to write the implementation. > Let's give a small hint: ORM and other SQL generators generate (maybe > database specific) SQL code just for the purpose that it is parsed back > into an execution tree one millisecond later. What is superfluous in > this scenario? Well, for simple applications that would be overkill. Also I have seen many places (even in big companies) where only JDBC is used. -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof