SQLite Lands JSONB For Much Faster JSON Functions

[cj.wijtmans]

I think bool should ne there atleast. Its 1bit(1byte) of data vs 8bytes or more

[patrick1946]

I think bool should ne there atleast. Its 1bit(1byte) of data vs 8bytes or more

Sqlite is encoding integer only to their size. So if it needs only one byte it is only using one byte. Like you can see there is even an optimization for 0 and 1.

Serial Type Codes Of The Record Format

0	0	Value is a NULL.
1	1	Value is an 8-bit twos-complement integer.
2	2	Value is a big-endian 16-bit twos-complement integer.
3	3	Value is a big-endian 24-bit twos-complement integer.
4	4	Value is a big-endian 32-bit twos-complement integer.
5	6	Value is a big-endian 48-bit twos-complement integer.
6	8	Value is a big-endian 64-bit twos-complement integer.
7	8	Value is a big-endian IEEE 754-2008 64-bit floating point number.
8	0	Value is the integer 0. (Only available for schema format 4 and higher.)
9	0	Value is the integer 1. (Only available for schema format 4 and higher.)
10,11	variable	Reserved for internal use. These serial type codes will never appear in a well-formed database file, but they might be used in transient and temporary database files that SQLite sometimes generates for its own use. The meanings of these codes can shift from one release of SQLite to the next.
N≥12 and even	(N-12)/2	Value is a BLOB that is (N-12)/2 bytes in length.
N≥13 and odd	(N-13)/2	Value is a string in the text encoding and (N-13)/2 bytes in length. The nul terminator is not stored.

[cj.wijtmans]

Well it is not only about storage its also about constraints a boolean is not simply an integer.

[patrick1946]

Well it is not only about storage its also about constraints a boolean is not simply an integer.

Hmm, in many languages a boolean is a integer. Actually can you describe the usecase? Sqlite is mostly used as am embedded database. And in most embedded usecases there is no big advantage for an extra bool type.

[cj.wijtmans]

Hmm, in many languages a boolean is a integer. Actually can you describe the usecase? Sqlite is mostly used as am embedded database. And in most embedded usecases there is no big advantage for an extra bool type.

no its not, in some cases a boolean can be stored as a single bit. In some cases booleans can be handled differently in different contexts as well, how strongly depends on the language. So no a boolean is not a simple integer.

[patrick1946]

no its not, in some cases a boolean can be stored as a single bit. In some cases booleans can be handled differently in different contexts as well, how strongly depends on the language. So no a boolean is not a simple integer.

https://en.cppreference.com/w/cpp/types/numeric_limits/is_integer

So in C++ it is a integer. I will not lookup other languages.

Sqlite is heavily used in embedded cases and there you use very often C++. So using a boolean as an integer is completely fine there.

[cj.wijtmans]

https://en.cppreference.com/w/cpp/types/numeric_limits/is_integer

So in C++ it is a integer. I will not lookup other languages.

Sqlite is heavily used in embedded cases and there you use very often C++. So using a boolean as an integer is completely fine there.

in C++ it can be either 1 bit or 1 byte or nothing at all. So again even if the underlying storage is an integer usually its not simply an integer. Not sure what you do not understand? There is a reason boolean is a seperate keyword these days.

[patrick1946]

in C++ it can be either 1 bit or 1 byte or nothing at all. So again even if the underlying storage is an integer usually its not simply an integer. Not sure what you do not understand? There is a reason boolean is a seperate keyword these days.

Okay, if even C++ type traits says it is an integer but you like to ignore it than...

https://stackoverflow.com/questions/4897844/is-sizeofbool-defined-in-the-c-language-standard

So the size is implementation defined but must be the size of a character or bigger. It can't be a bit because a bit has no address. You can use bit fields but that bit field has a type and must be the size of the type. Why it can't be a bit? Because you can't address a bit in memory.