Bun and NodeJS return different results for the same SQLite query

Until the other day, I didn't even think this was possible. The same language, the same database, and the same query returning different results.

Take this SQL:

select 3 / 2;

The result turns out to be 1 because SQLite and most other databases treat this as integer arithmetic. Both bun and node return the result as 1 also:

Here is the node version:

import { DatabaseSync } from 'node:sqlite';

const db = new DatabaseSync(':memory:');
const statement = db.prepare('select 3 / 2 as result');
const result = statement.get();

console.log(result); // { result: 1 }

Now, let's pass the 2 in as a parameter instead using node:

import { DatabaseSync } from 'node:sqlite';

const db = new DatabaseSync(':memory:');
const statement = db.prepare('select 3 / ? as result');
const result = statement.get(2);

console.log(result); // { result: 1.5 }

The result has changed to 1.5.

Let's try it with bun:

import { Database } from 'bun:sqlite';

const db = new Database(':memory:');
const statement = db.prepare('select 3 / ? as result');
const result = statement.get(2);

console.log(result); // { result: 1 }

The same query, the same database, and the same language, but different results.

Why is this the case? It turns out that node chooses to bind all number parameters using sqlite3_bind_double regardless of whether they are mathemetical integers or not. Bun, on the other hand, decides to use sqlite3_bind_int or the 64-bit version of this if the value is actually an integer.

Who is right? One argument from the node camp is that

JavaScript doesn't have an integer type so all numbers should be bound to statements as doubles

Everyone knows this right? All the smart people do at least. JavaScript doesn't have an integer type! It is true, but does JavaScript have the concept of integers? This is a different question. The answer is yes.

const shift = 5 << 1;

What is 5? It is very specifically an integer in this context, so the debate cannot end there. When you ask somebody what the 2 is in this code, what will they say?

const result = statement.get(2);

"It is a number". "What kind of number?", you ask. "An integer".

It still seems entirely up for debate as to what the correct approach is. The fact that taking a number out of the statement and turning it into a parameter results in a different outcome is maybe the best case for binding integers as integers.