Generator-jhipster: Make PostgreSQL the default in JHipster 6

[mraible]

Because it’s awesome and we know it.

http://www.craigkerstiens.com/2018/09/20/postgresql-11-a-first-look/

[sendilkumarn]

👍 ( for production right? 😉)

[atomfrede]

+1 Maybe we can also get rid of dev/production separation. We use testcontainers already for e.g. couchbase, why not use it postgres etc. too? We already rely a lot on docker(compose) so it is not a big problem imho.

[deepu105]

We could but only problem is then in dev you need one more step to start
the app. Also h2 is much better when you are prototyping something and want
to recreate db all the time.

On Sat, 22 Sep 2018, 8:37 am Frederik Hahne, [e-mail]
wrote:

+1 Maybe we can also get rid of dev/production separation. We use
testcontainers already for e.g. couchbase, why not use it postgres etc.
too? We already rely a lot on docker(compose) so it is not a big problem
imho.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jhipster/generator-jhipster/issues/8384#issuecomment-423721319,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDlF1MSCRpwYprDVyJ1nOJSX0007rs5ks5uddq2gaJpZM4W1CDL
.

[atomfrede]

That's right. We should gather some statistics how many choose same production and development databases.

[agoncal]

@deepu105 I like the idea of @atomfrede to gather some statistics. In the past I had so many issues with having different DBs in dev/prod that now I always use Postgres in dev/prod (much easier now with containers)

[atomfrede]

And if we use test containers for unit tests we have the same experience as before except removing/clearing data during development. But I am sure we can e.g. always reset the date in dev profile for example or provide a special flag when starting the application.

[sendilkumarn]

@atomfrede with h2 as a default option, I think that will win hands down 👍

But I agree with @deepu105 here that we need to have h2 to make sure that in prototyping it is always a single step to get started

[jdubois]

For production -> I think we all agree here. I'm closing this as there's no need to keep the ticket opened for months, just to remember this. Let's use the "v6" tag as @deepu105 did, and we'll need to read the issues when we start v6 (maybe next spring?)
For dev I'm quite happy with H2, at least it provides a great "out of the box" experience for developers, which is our #1 goal. Then, we can't expect everyone to have Docker - most of my customers, including those speaking at lot about Docker in conferences and in the press, can't use Docker on their dev machines as they are locked, and with old Windows versions. So that's just not possible at the moment.