-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while doing a MapScan or SliceScan time.Time with PostgreSQL #59
Comments
|
Yes, this is a bug. The way edit: The map[string]*string interface is a lot more convenient than map[string]interface{} for most cases where MapScan is actually a good API, because you won't have a good idea of what the types are and a string representation is probably good enough. Still it's probably good enough to let |
Do you have a suggestion for a workaround? Maybe you can also add this to the documentation for now. In case of a SELECT * FROM A you don't know what type you are selecting so as far as i know there is no place for a to_char. |
@frankbb Fixing this is ironically a breaking change. I will create a branch for you to use which fixes this while I gather a bunch of planned breaking changes together for a single release + announcement. Even though the current behavior is convenient, I think it is wrong. It's also unnecessarily opinionated to coerce everything to |
Great, thanks i will try that branch, if i run into bugs i will let you know. |
This has been integrated into master now, along with many other fixes. |
Not really sure if it's a sqlx issue. When i use a MapScan or a SliceScan in combination with a Postgresql timestamp field it will result in a scan error, or did i miss something?
Error:
Database Postgresql column:
The text was updated successfully, but these errors were encountered: