We are very excited to be working with two fantastic GSoC contributors this year: Yutan Yang (@tarotaroyoung) and Zhenglin Li. Learn more about them at sqlancer.github.io/blog/gsoc….
We are excited that the @CnosDB development team contributed support for testing CnosDB to SQLancer! github.com/sqlancer/sqlancer…
Fun fact: in terms of the number of commits, @dependabot is the 2nd and 3rd most active committer to SQLancer. Thank you, @dependabot!
Woohoo! SQLancer has been starred 1,000 times. Thank you everyone for your support! github.com/sqlancer/sqlancer…
Andrey Lepikhov found an interesting bug in Postgres by extending SQLancer to support testing Postgres extensions (see github.com/sqlancer/sqlancer…).
postgresql.org/message-id/fl…
Interested in working on a project related to @sqlancer_dbms as part of #GSoC2022? A project mentored by @estet is to integrate SQLancer with @TarantoolDB! github.com/tarantool/taranto…
SQLancer is becoming more friendly to database implementations that are being developed outside of its repository. The first step: SQLancer picks up DatabaseProvider implementations in any JARs that are on the classpath using Java's ServiceLoader feature. github.com/sqlancer/sqlancer…
Ternary Logic Partitioning (TLP) and the other testing techniques that SQLancer implements can be combined with other SQL generators as well. For example, have a look at @CockroachDB's TLP implementation! github.com/cockroachdb/cockr…
Interested in contributing to SQLancer? Adding support for testing @QuestDb would be a valuable contribution! github.com/questdb/questdb/i…
SQLancer surpassed the 800 stars mark and has been receiving an increasing number of external contributions. Thanks, everyone!
SQLancer is now using GitHub Actions for its CI tests. Thanks for running our tests until recently, @travisci!
2
Learn about SQLancer and its testing techniques in the REBASE talk that is online at youtube.com/watch?v=lCaGWSk5….
Thanks @PTKDaily, for featuring SQLancer in your newsletter! mailchi.mp/amplifypartners.c…
SQLancer has been starred 500 times on GitHub. Thank you for your support! github.com/sqlancer/sqlancer
Consider this test case, for which MySQL computed an incorrect result. After removing the double negation, the comparison 123 != 123 incorrectly evaluated to FALSE. The expression NOT NOT 123 should have computed 1, and should have caused the row to be fetched.
A classical algebraic optimization described in "Query Optimization in Database Systems" is to simplify an expression NOT NOT A to A. Can you think of a DBMS and scenario where this optimization is invalid? dl.acm.org/doi/10.1145/35692…
1
3



















