Binary representation exists in JavaScript

And many other languages besides (such as Python and Tcl).

Which isn't to make an argument for or against in this case.

Which isn't to make an argument for or against in this case.

You may not have wanted to make an argument, but, by saying so, you did. And for it. :-)

This seems like a good candidate for a binary() user defined function.

Actually no, SQLite does not support any representation other than base-10.

You may use base-16 input tokens and they will (mayhaps) be interpreted correctly, bu you may not use base-16 representation of values (well, actually you can, but they are just a bag-o-bytes (that is, 0xffff is a text string bag of bytes, not a number)).

Are you suggesting that you wold want base-2 input tokens (not values). What about base-8 input tokens (not values).

Or are you somehow under the misunderstanding that SQLite recognized base-16 values rather than merely base-16 tokens?

0xffff is a text string bag of bytes, not a number

This is the SQLite forum, not the MySQL forum.

sqlite> select typeof(0xffff);
+----------------+
| typeof(0xffff) |
+----------------+
| integer        |
+----------------+

Exactly. SQlite3 only allows use of hexidecimal notation in tokens, not values.

SQLite version 3.42.0 2023-04-03 04:59:10
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> create table x(x integer);
sqlite> insert into x values (0xffff);
sqlite> select x, typeof(x) from x;
┌───────┬───────────┐
│   x   │ typeof(x) │
├───────┼───────────┤
│ 65535 │ 'integer' │
└───────┴───────────┘

You will note that the value of x is the integer 65535, not the token-string 0xffff. You can convert the integer 65535 to the character-token-string 0xffff, but then it is a bag-o-bytes text string, not an integer.

sqlite> select y, typeof(y) from (select format('0x%x', x) as y from x);
┌──────────┬───────────┐
│    y     │ typeof(y) │
├──────────┼───────────┤
│ '0xffff' │ 'text'    │
└──────────┴───────────┘

SQLite does not support any representation other than base-10. ...

The docs say hexadecimal literals are accepted.

Yes, not hexideciaml values.

Actually no, SQLite does not support any representation other than base-10.

Actually, SQLite integers are represented with sixty-four digits using base two.

Actually, SQLite integers are represented with sixty-four digits using base two.

Actually, the cell representation is often less than 64 bits.

At a lower level, the representation is often higher than or lower than nominal charge in a few femptoFarads of capacitance, or relative positions of minute region magnetic flux reversals.

Would that take into account allowances for quantum-affected variations?

REg4rd5, br!ckv1King

(Post 10)

Would that take into account allowances for quantum-affected variations?

Not quite, as stated. I just find it amusing to see "actually" associated with the imaginary "bits". We wish they were truly binary, but reality intervenes with finite Signal-to-Noise-Ratio, quantum effects and uncertainties, and occasional cosmic rays.

SQLite does not support any representation other than base-10.

As I read it, this request isn't about the representation in storage, but the textual representation as a literal value in an SQL script. That is, it is an SQL parser matter and not something that the bytecode engine (or below) need to care about at all.

Yes, exactly.