Feat: custom select on customTypes

[Angelelz]

This PR will close #554 and will close #1083.

I have added a new API for customTypes that allows wrapping the column name with custom sql. The syntax is the following:

const getAsLower = customType<{
  data: string;
}>({
  dataType: () => "text",
  customSelect: (column) => sql`lower(${column})`
});

You can then use the customType as follows:

export const users = mysqlTable("users", {
  id: int("id").autoincrement().primaryKey(),
  name: text("name").notNull(),
  lowercase: getAsLower("lowercase").default(sql`(\`name\`)`),
  managerId: int("manager_id")
    .references((): AnyMySqlColumn => users.id)
    .$default(() => 1),
});

Then, a select like this:

const q = await db.select().from(users);

Will result in the following query:

select `id`, `name`, lower(`lowercase`) as `lowercase`, `manager_id` from `users`

Notice how as opposed to the suggestion in #1083 it's not necessary to define a mapWith or an alias.
By default, the column will be aliased to the column name, and the custom decoder can be defined the usual way with fromDriver.

/claim #554
/claim #1083

[mauriciabad]

1st of all, thanks for your work on this library!

After that said, check out the 2 comments, they may be worth solving before merge, but if you want you can merge and tackle them in a following PR.

Another suggestion I have is to add the pertinent explanations in the documentation, so this feature is discoverable and developers know it exists and how it works. I assume this will be done in a separate PR, but I mention it anyway.

I'm specially interested on this feature because I'm developing a project that will use geospatial data (POINT and more).
And, I'm more than happy to help if needed, although I'm not familiar with Drizzle's codebase, I may still be useful. 😊

[ronnostic]

LGTM!

[fvaldes33]

Getting this merged would be amazing. Working on custom PostGIS types and not having this is a big blocker.

Thanks for the work on this @Angelelz

[mauriciabad]

Same, here. I also use geospatial data and this is needed.

[hauserkristof]

Please merge this! This would be super useful, especially in spatial applications!

[mauriciabad]

@AlexBlokh @AndriiSherman @dankochetov @Angelelz please take a look

[bernatfortet]

@Angelelz any chance you can marge this?

[Angelelz]

Only core team member can merge PRs. Just upvote and wait for when they have time to review.

[balloman]

Is there any feedback from the drizzle team on this, at least? It seems there is pretty widespread support for this, and It's pretty disheartening from a library to see an issue you encounter has been pending for 6+ months. Will this get resolved? Are the devs uninterested in supporting this feature? Is there something wrong with the code? At least some background would be useful to understand next steps for builders.

[dankochetov]

Unfortunately, we don't have enough capacity to look into this currently, but we agree that this is a useful feature and it will be eventually resolved.

[mwanago]

This feature would be super useful!

[robinsimonklein]

Any news about this ?

[shahzaib-cmyk]

This would have been very helpfull in my current project. Any idea when progress might be made?