Olivier Mengué
Olivier Mengué
Yes, NullTime (as well as time.Time) works with `TIMESTAMP` columns like `DATE` and `DATETIME`.
Related: #960 (deprecate NullTime with Go 1.13)
Please add the Go code that shows how you query the current charset and the current collation.
``` var collation string db.QueryRow(`SELECT @@collation_connection`).Scan(&collation) fmt.Println("Collation:", collation) ```
Note that the [documentation for `charset`](https://github.com/go-sql-driver/mysql#charset) says: > Usage of the `charset` parameter is discouraged because it issues additional queries to the server. Unless you need the fallback behavior, please...
@methane Users can be wrong, despites a good intent (specifying both `charset` and `collation` in a connection string looks good until you read the documentation). Worse: the fact that `charset`...
This can be implemented by writing another `sql.Driver` that wraps the the original driver. As a demonstration, see my own driver [`github.com/dolmen-go/mylogin-driver`](https://pkg.go.dev/github.com/dolmen-go/mylogin-driver/?tab=doc) that reads host/port/user/password from `~/.mylogin.cnf`.
The CLDR has [day of week names](http://cldr.unicode.org/translation/date-time-names). The [i18n-dateformatter](/altipla-consulting/i18n-dateformatter) project may be helpful to use them (but I've not really dug into it).
The label "bug" for this issue would be more appropriate than "enhancement". Also, the README claims that "Tokei is accurate". So, is this issue fixed?
This should fix #22.