You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue, but a proposal to have the json extension loaded by default into the driver.
I'm currently developing a framework/library that requires the go-sqlite3 with the json extension loaded, and while you could build it with -tags json1, this also requires the consumers of my library to pass the same build tags when building their project which results in a poor dev experience.
This topic was brought several times in the past (ex. #710, #832 and golang/go#43288) and since the json extension is frequently used, I want to suggest enabling it by default. As Russ Cox mentioned in the related go issue, I don't think this will increase the size significantly and will result in better out-of-the-box dev experience when using the driver.
The text was updated successfully, but these errors were encountered:
Actually, after reading the release notes of SQLite 3.38.0, it seems that the JSON functions are already built-ins and the SQLITE_ENABLE_JSON1 option is a no-op.
This is not an issue, but a proposal to have the json extension loaded by default into the driver.
I'm currently developing a framework/library that requires the go-sqlite3 with the json extension loaded, and while you could build it with
-tags json1
, this also requires the consumers of my library to pass the same build tags when building their project which results in a poor dev experience.This topic was brought several times in the past (ex. #710, #832 and golang/go#43288) and since the json extension is frequently used, I want to suggest enabling it by default. As Russ Cox mentioned in the related go issue, I don't think this will increase the size significantly and will result in better out-of-the-box dev experience when using the driver.
The text was updated successfully, but these errors were encountered: