Implementing a SurrealDB driver; where is what?

[IngwiePhoenix]

Hello there!

I have already written the database/sql[/driver] implementation for SurrealDB - but now I would like to add some ORM features, which I initially attempted to do with Gorm... but, just look at this spaghetti code, and you know why I am stuck: https://github.com/IngwiePhoenix/surrealdb-driver/blob/f0fa9b7b9dde2a164e7c49287f1df99938561d60/pkg/gorm/migrator.go

I did my very best trying to work off of their existing drivers and their godoc, but, I am hopelessly stuck and it appears that community support is quite sparse... so, I looked for other ORMs, and ended up here :)

So, I want to try to write an adapter for rel. Looking at the MySQL one, I see this: https://github.com/go-rel/mysql/blob/main/mysql.go#L39-L50

My questions are:

• SurrealDB has a few syntaxes that are rather incompatible by default. For example, REMOVE is the sort-of equivalent to DROP for most things, whilst SELECT straight up lacks JOIN and instead uses record links, graph edges and other syntaxes. How do I implement a custom syntax off of one of those builder structs?
• Looking at the custom column mapper, how do I map some of SurrealDB's types? For example, there are built-in types for GeoJSON. How do I establish the type mapping? My driver has aliased a compatible type already - can I just reuse that?

Thank you and kind regards,
Ingwie

[Fs02]

SurrealDB has a few syntaxes that are rather incompatible by default. For example, REMOVE is the sort-of equivalent to DROP for most things, whilst SELECT straight up lacks JOIN and instead uses record links, graph edges and other syntaxes. How do I implement a custom syntax off of one of those builder structs?

I think you either need to send PR to https://github.com/go-rel/sql to support SurrealDB flavor, or create a custom sql builder

Looking at the custom column mapper, how do I map some of SurrealDB's types? For example, there are built-in types for GeoJSON. How do I establish the type mapping? My driver has aliased a compatible type already - can I just reuse that?

yes, I think so
there's no strict definition for JSON at the moment

REL have embedded structs, but I don't think that's what you want