-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use MySQL on development and production? #3170
Comments
aha - sorry, i should've caught that! Hmm, so we've traditionally used
sqlite because it's such an easy install (by default already available on
Macs, I think?) but this has come up before, and I agree it's a frustrating
issue.
I wonder if we could think about how to remind ourselves about the database
differences - so when this does happen, there's some clue to what's
happening... i don't know, do you think there's an approach like that which
could work?
But i'm not set on either way, i just want to think through this carefully.
…On Wed, Aug 1, 2018 at 12:01 AM Stefanni ***@***.***> wrote:
@milaaraujo <https://github.com/milaaraujo> and I were having some errors
on travis even having our checks all green locally. We asked our coaches to
help us and we were able to fix the error (#3134
<#3134>). We were doing full text
search, to give more context.
The problem was that locally, we were using SQLite3 and travis uses maria
db, so the query was not returning the same results.
Is it possible to have a unique and consistent database type for
development and production? What do you think? We believe this may improve
the future contributions for the project :)
we found some links that might be useful for this here
<https://stackoverflow.com/questions/29743444/rails-databases-why-use-same-dbms-for-development-and-production>
and here
***@***.***/rails-db-lesson-learned-e416e2f2549c>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3170>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJy-wZW_bFU9V59sPpDtritXXHw4sks5uMSgAgaJpZM4Vpzrm>
.
|
I think we could at least have this better documented in a place, like mention in the installation guide that we use different database type for development and production. |
I added this to the Testing docs file #3483 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@milaaraujo and I were having some errors on travis even having our checks all green locally. We asked our coaches to help us and we were able to fix the error (#3134). We were doing full text search, to give more context.
The problem was that locally, we were using SQLite3 and travis uses maria db, so the query was not returning the same results.
Is it possible to have a unique and consistent database type for development and production? What do you think? We believe this may improve the future contributions for the project :)
we found some links that might be useful for this here and here.
The text was updated successfully, but these errors were encountered: