5 ms·

Then one day a better embedded db comes along and people forget about sqlite.

deleted 5y ago
[deleted]
lifeisstillgood 5y ago
Maybe. But we learn from the sheer hard work put into this level of testing. And having this level of testing makes you put a bit more effort into each new line. The bar has been raised. If someone is to make a better embedded DB, they will have to maintain it at least as well as this. (PS I feel embarrassed by my own testing failures when reading this).
henning 5y ago
Since SQLite is in every iOS and every Android device along with the Python standard library, I don't think it will be forgotten quickly.
zepto 5y ago
Such as?
karmasimida 5y ago
That DB better inherit those test cases however, those are incredible assets
- luto 5y ago
  It can't. Most of that test code is proprietary to the SQLite team and not available to others.
  - jayd16 5y ago
    Interesting. Why do you think that is?
    - avhon1 5y ago
      A large amount of the testing is performed by their proprietary test harness. > TH3 consists of about 71.5 MB or 978.3 KSLOC of C code implementing 46622 distinct test cases. TH3 tests are heavily parameterized, though, so a full-coverage test runs about 1.9 million different test instances. The cases that provide 100% branch test coverage [of SQLite] constitute a subset of the total TH3 test suite. [1] > SQLite itself is in the public domain and can be used for any purpose. But TH3 is proprietary and requires a license. > Even though open-source users do not have direct access to TH3, all users of SQLite benefit from TH3 indirectly since each version of SQLite is validated running TH3 on multiple platforms (Linux, Windows, WinRT, Mac, OpenBSD) prior to release. So anyone using an official release of SQLite can deploy their application with the confidence of knowing that it has been tested using TH3. They simply cannot rerun those tests themselves without purchasing a TH3 license. [2] [1] https://sqlite.org/testing.html https://sqlite.org/testing.html [2] https://sqlite.org/th3.html https://sqlite.org/th3.html
    - kevin_thibedeau 5y ago
      They don't have an open development model. Controlling the test harness prevents a viable fork. That is their moat that ensures a revenue stream.
    - simonw 5y ago
      It's a great business decision. My understanding is that SQLite's big consulting income comes when some company somewhere produces a new piece of embedded hardware and needs SQLite to work on it. They can work directly with the company to get that to happen, using the company's proprietary testing suite.
  - avhon1 5y ago
    They do sell licenses to their proprietary test harness. https://sqlite.org/prosupport.html https://sqlite.org/prosupport.html

deleted 5y ago

[deleted]

Maybe. But we learn from the sheer hard work put into this level of testing. And having this level of testing makes you put a bit more effort into each new line. The bar has been raised. If someone is to make a better embedded DB, they will have to maintain it at least as well as this. (PS I feel embarrassed by my own testing failures when reading this).

henning 5y ago

Since SQLite is in every iOS and every Android device along with the Python standard library, I don't think it will be forgotten quickly.

zepto 5y ago

Such as?

karmasimida 5y ago

That DB better inherit those test cases however, those are incredible assets

luto 5y ago
It can't. Most of that test code is proprietary to the SQLite team and not available to others.
- jayd16 5y ago
  Interesting. Why do you think that is?
  - avhon1 5y ago
    A large amount of the testing is performed by their proprietary test harness. > TH3 consists of about 71.5 MB or 978.3 KSLOC of C code implementing 46622 distinct test cases. TH3 tests are heavily parameterized, though, so a full-coverage test runs about 1.9 million different test instances. The cases that provide 100% branch test coverage [of SQLite] constitute a subset of the total TH3 test suite. [1] > SQLite itself is in the public domain and can be used for any purpose. But TH3 is proprietary and requires a license. > Even though open-source users do not have direct access to TH3, all users of SQLite benefit from TH3 indirectly since each version of SQLite is validated running TH3 on multiple platforms (Linux, Windows, WinRT, Mac, OpenBSD) prior to release. So anyone using an official release of SQLite can deploy their application with the confidence of knowing that it has been tested using TH3. They simply cannot rerun those tests themselves without purchasing a TH3 license. [2] [1] https://sqlite.org/testing.html https://sqlite.org/testing.html [2] https://sqlite.org/th3.html https://sqlite.org/th3.html
  - kevin_thibedeau 5y ago
    They don't have an open development model. Controlling the test harness prevents a viable fork. That is their moat that ensures a revenue stream.
  - simonw 5y ago
    It's a great business decision. My understanding is that SQLite's big consulting income comes when some company somewhere produces a new piece of embedded hardware and needs SQLite to work on it. They can work directly with the company to get that to happen, using the company's proprietary testing suite.
- avhon1 5y ago
  They do sell licenses to their proprietary test harness. https://sqlite.org/prosupport.html https://sqlite.org/prosupport.html