Feature/add bson column type

[Rodriguespn]

Support bson column type for

• drizzle-kit
• drizzle-orm
• drizzle-typebox
• drizzle-valibot

Includes a set of tests for singlestore and a green pipeline is expected

Note: When defining the default value of a bson type column during table creation, the default value of the column is converted to hexa code to be accepted by the engine.

The CREATE TABLEstatement generated by drizzle-kit for the default value of {"key":"value"} will be

CREATE TABLE `table` (
        `bson` bson DEFAULT 0x14000000026b6579000600000076616c75650000 /* hexa code for {"key":"value"} */
);

The SingleStore team is working to accept json literals for bson columns default values.

This would work in the future

CREATE TABLE `table` (
        `bson` bson DEFAULT '{"key":"value"}'
);

When the json literals are supported we can simplify the code and remove the BSON external package.

[mitchwadair]

nit: rm log

[Rodriguespn]

Nice catch 👍

[mitchwadair]

I'm curious about how we want to represent the data here. Do we expect users to be dealing with BSON data in a manner like this, or are we expecting them to convert it to JSON anyways? Especially considering the to-driver stuff is using JSON.stringify

[Rodriguespn]

From my perspective, the ideal scenario is that users deal only with JSON strings and let the form deal with the translation. That would make things more easy for users.

Something like:

db.singlestoreTable({
  ...
   bson_column: bson().notnull().default({"key": "value"})
   ...
 }) 

Currently there is a bug on the translation of literals into BSON on the engine side, so this will only be possible once the bug on the engine is fixed. For now the default value has to be converted to BSON object and then to hexa string

More info about the bug on slack: https://memsql.slack.com/archives/C02G51BAJ/p1724069568691219?thread_ts=1724061645.083329&cid=C02G51BAJ

I also found out that you can cast json literals on select and insert statements, but not on create table statements. Because of that, we can keep the jsonString:>BSON on the mapToDriver return value, since the drizzle-orm package only deals with insert and select operations, and the option above on drizzle-kit, that deals with scheam modifications (create table and create/alter column)

[mitchwadair]

Yeah, that all makes sense from the engine side. I guess I was more curious about the JS side of when we get the data out from the engine. Do we expect users to use BSON directly in TypeScript or should we also convert it back to JSON?

[mitchwadair]

reminder to add back the removed BSON column type from #11 to this PR