Earlier quoted context omitted.
Ditto! For anyone who isn't familiar with SQLite's testing procedures, read this[1] fascinating page. The SQLite project has a mind boggling 711 times more test code than SQLite itself has. Put another way, only 0.1% of the project's code is SQLite itself. The other 99.9% consists of tests for that 0.1%. [1] https://www.sqlite.org/testing.html
Good thing too, since it's in just about everything: https://www.sqlite.org/mostdeployed.html
SQLite Release 3.25.0 adds support for window functions
31–40 of 116 posts
Re: SQLite Release 3.25.0 adds support for window functions
#32Earlier quoted context omitted.
Ditto! For anyone who isn't familiar with SQLite's testing procedures, read this[1] fascinating page. The SQLite project has a mind boggling 711 times more test code than SQLite itself has. Put another way, only 0.1% of the project's code is SQLite itself. The other 99.9% consists of tests for that 0.1%. [1] https://www.sqlite.org/testing.html
Good thing too, since it's in just about everything: https://www.sqlite.org/mostdeployed.html
Re: SQLite Release 3.25.0 adds support for window functions
#33A bit offtopic but has anyone tried to replicate sqlite databases? Using rqlite https://github.com/rqlite/rqlite or something else?
Re: SQLite Release 3.25.0 adds support for window functions
#34Earlier quoted context omitted.
I just checked a stripped copy of postgresql-10 built with all options on and it is 7MB. That could be reduced a little by leaving out language support and ssl support etc.
Do you have tutorials to strip lang and ssl? Is it possible to dynamic link system openssl to reduce size?
It is dynamically linked to openssl, but you can configure out the internal code to support the functionality.
"strip" however meant the unix strip command to remove debug symbols.
Re: SQLite Release 3.25.0 adds support for window functions
#35Earlier quoted context omitted.
I just checked a stripped copy of postgresql-10 built with all options on and it is 7MB. That could be reduced a little by leaving out language support and ssl support etc.
While binary size could certainly be a factor in a good deal of embedded environments, we also need to look at the resource requirements of the binary in question as well. Sqlite doesn't need too much more memory than what its binary needs whereas with postgresql, you need all sorts of bells and whistles just to get the database system to boot.
Anyway, not trying to make the case that postgresql is small compared to sqllite, it obviously isn't, just wanted to point out that it's not _that_ big either.
Re: SQLite Release 3.25.0 adds support for window functions
#36Earlier quoted context omitted.
Well if you don't mind rewriting tables, just create a table in the new structure, insert data from the old table to the new one, drop the old table, and rename the new table.
That’s not enough because it ignores all foreign key constraints.
Re: SQLite Release 3.25.0 adds support for window functions
#37I’d really really like if they improved “alter table” to include dropping/renaming columns/constraints, even if it required rewriting the whole table.
There is nothing stopping you from doing it yourself. The Sqlite FAQ[1] even has an entry on it. Two things holding this back: 1. code being inside our outside sqlite would not be much different. 2. the amount of additional test code would be humongous for an operation of that level of complexity. So, just do it yourself. It's not that hard. [1]: https://www.sqlite.org/faq.html#q11
Re: SQLite Release 3.25.0 adds support for window functions
#38Earlier quoted context omitted.
Well if you don't mind rewriting tables, just create a table in the new structure, insert data from the old table to the new one, drop the old table, and rename the new table.
One problem is that you then might need a special case for SQLite in migrations which can lead to different db schemas in tests and production
Re: SQLite Release 3.25.0 adds support for window functions
#39I’d really really like if they improved “alter table” to include dropping/renaming columns/constraints, even if it required rewriting the whole table.
Well if you don't mind rewriting tables, just create a table in the new structure, insert data from the old table to the new one, drop the old table, and rename the new table.