Defaulting to the use of one DBMS

[siaw23-retired]

I've been away from plots2 for a while. Coming back and following the README I found it cumbersome to get up to running quickly because there are traces of a number of database management systems in plots2. This makes it hard to set up and have tests running smoothly.

It'd be nice to have one DBMS for all to avoid the configuration headache encountered through this. I believe this will get new contributors up and running quickly and encourage more contribution from people as I think the current multi-db setup/config is a bit intimidating considering we like to welcome first-time coders on board.

I think once this is acceptable to everyone and we get to implement this, we can completely avoid #3840 where @milaaraujo correctly states:

Getting set up can be tough.

Setup is the last thing we want to make hard for new contributors.

[jywarren]

thanks everyone for the great input here! One last thing before we make a final decision - does someone want to ask in the next weekly Check-In what databases people use? Especially first-timers? It'd be great to have extra confirmation - do most newcomers use mysql or sqlite?

…

On Fri, Mar 1, 2019 at 6:57 AM Emmanuel Hayford ***@***.***> wrote: I've been away from plots2 for a while. Coming back and following the README I found it cumbersome to get up and running quickly because there are traces of a number of database management systems in plots2. This makes it hard to set up and have tests running smoothly. It'd be nice to have one DBMS for all to avoid the configuration headache encountered through this. I believe this will get new contributors up and running quickly and encourage more contribution from people as I think the current multi-db setup/config is a bit intimidating considering we like to welcome first-time coders on board. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4896>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJwLIb--1cZwbxtXM84jWtEQ03ltYks5vSRVvgaJpZM4bY3P_> .

[grvsachdeva]

Nice idea @jywarren. Also, many contributors faced issues while getting started with Mapknitter due to MySQL - publiclab/mapknitter#307.

How about a poll? @siaw23 @jywarren

[jywarren]

+1!

…

On Fri, Mar 1, 2019 at 10:48 AM Gaurav Sachdeva ***@***.***> wrote: Nice idea @jywarren <https://github.com/jywarren>. Also, many contributors faced issues while getting started with Mapknitter due to MySQL - publiclab/mapknitter#307 <publiclab/mapknitter#307>. How about a poll? @siaw23 <https://github.com/siaw23> @jywarren <https://github.com/jywarren> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4896 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJ_9R8-bIsKCS6d08jgyBOuyAKoZHks5vSUubgaJpZM4bY3P_> .

[siaw23-retired]

Personally I find it unnecessary to create a poll. We use MySQL in production, so, if people vote SQLite, are we are going to switch from MySQL to SQLite? Or are we still going to keep SQLite and MySQL (still multiple DB problems here if people want SQLite).

IMHO we should use the DB that we have in production locally for development (installing MySQL/MariaDB is fairly easy and there are lots of docs for newbies who'd get lost). I updated the README in my PR that shows how to get MariaDB running on Mac and Ubuntu. And by the way I think SQLite should be out completely because I think there has been some added raw SQL queries that won't work on SQLite. This raw SQL here among others is an example.

[jywarren]

I think we could ask just to know especially who we'd be asking to switch over - and actually we could point them at your PR readme additions and ask them to try going through the steps to see if there are any common pitfalls? Mainly we just don't know currently if there are people using sqlite, or if perhaps almost everyone uses mysql and we shouldn't be worrying about it. Thanks!

…

On Fri, Mar 1, 2019 at 11:31 AM Emmanuel Hayford ***@***.***> wrote: Personally I find it unnecessary to create a poll. We use MySQL in production, so, if people vote SQLite, are we are going to switch from MySQL to SQLite? Or are we still going to keep SQLite and MySQL (still multiple DB problems here if people want SQLite). IMHO we should use the DB that we have in production locally for development (installing MySQL/MariaDB is fairly easy and there are lots of docs for newbies who'd get lost). I updated the README in my PR that shows how to get MariaDB running on Mac and Ubuntu. And by the way I think SQLite should be out completely because I think there has been some added raw SQL queries that won't work on SQLite. This raw <https://github.com/publiclab/plots2/blob/master/app/models/user.rb#L385> SQL here among others is an example. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4896 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJ3WRbkAniK0tbrRunv-BWgS7Tt38ks5vSVXMgaJpZM4bY3P_> .

[siaw23-retired]

OK. Sounds good then.

[milaaraujo]

I think the poll is a good idea! But I agree 100% with @siaw23 that we should use the DB that we have in production locally for development. :)

[jywarren]

Just noting that @stefannibrasil and @sashadev-sky have also both voiced support for dropping sqlite -- here! #2712 (comment)