What's something you wish databases would do better?
-
-
Replying to @yoshuawuyts
Mocking. Every time you need to test your application you need to figure out how to mock the database, it is such a common issue. If every database would ship an official/easy way to mock it, it would be great :)
1 reply 1 retweet 21 likes -
Replying to @delvedor
Ohh, thanks for sharing! It sounds like "testing" should be considered a first-class workflow. Do you have any examples of DB mocking packages you like?
2 replies 0 retweets 2 likes -
Replying to @yoshuawuyts
Yes, probably testing is the correct phrasing :) Regarding the modules, there is https://github.com/nearform/no-gres … from
@NearForm, which is rather nice. For the Elasticsearch and Node.js, I wrote this https://www.elastic.co/blog/smooth-mocking-with-the-elasticsearch-node-js-client ….1 reply 0 retweets 1 like -
The main issue is that mocking is very language-dependent, and you risk to mock too much or too little, so provide a good way to do it isn't that easy.
1 reply 0 retweets 1 like -
I always hit nasty surprises when mocking databases - I have since switched to using a proper DB and isolating each test using either transactions or separate logical DBs.
1 reply 0 retweets 3 likes -
Replying to @algo_luca @delvedor and
The latest one was last week, when we tuned a query, all tests were green, deployed,
Tests were using the in memory db provided by Entity Framework which does not behave like Postgres in that instance
1 reply 0 retweets 1 like
All of this. Even when not testing, I shouldn't have to run a separate process, much less a server or cluster, to build on the semantics of an RDBMS. SQLite does okay at this.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.