-
Notifications
You must be signed in to change notification settings - Fork 94
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
Add: Support for Postgres #288
Comments
Yes please @swhyte-rt! Was it just adding the config options? We tried to keep the SQL compatible across the major databases. |
It was adding config options, but also supporting differences in queries. For example Postgres did not like
so I had to change to
I will test this one more time, but it was throwing error when preparing the statement. |
Here is the documentation explaining that most DB will support |
Ah that's too bad. Did you have to branch at each query off a config or flag? |
I have repository interfaces, and have implemented a |
@adamdecaf I can let you look at the fork of the work if you want to look at it before doing a pull request. |
Sure! I think it's this branch? |
Yep that is it |
@adamdecaf I may have been over thinking this by breaking out separate repositories for generic db and Postgres. I was thinking if you were to ever support nosql databases. I can change this to a single repository with constants for the various queries and check the db type when initializing the query. That would be cleaner. |
We have no plans to support NoSQL for storage in Watchman. One repository for all three databases sounds fine so long as we find/replace and always prepare the query. I was checking with other projects and they've written an implementation for MySQL and Postgres. |
Watchman Version:
current version and forward
What were you trying to do?
Run watchman with Postgres as Database
I am just finishing off the implementation of this and can create a pull request.
The text was updated successfully, but these errors were encountered: