-
Notifications
You must be signed in to change notification settings - Fork 189
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
how to use qor admin with gorm.io/gorm #251
Comments
Yeah I think qor needs to be updated to support gorm 2. It seems all development of gorm has shifted to the new version. |
hi @hpdipto What specific feature do you want to use in gorm 2.0? We do have a plan to migrate qor to gorm 2.0, but haven't evaluated the impact and benefit. it would be helpful if you can show us your requirement. |
Actually I can't mention very specific feature of gorm 2.0 that I want to use. But why should I incorporate an old version in my code base? |
Gorm 2 has a host of new useful features like batch insert better clause support and more. We want to move to it so we get continued support and to get access to all the other features. |
any updates? |
Do we have an update on this please? Gorm 1.9 has been dead for over a year and is pinned to use a version of a postgres driver that is 14 months or so older than that. |
Any updates? |
I'm trying to add Qor to an existing code base. My existing code has been ported to Gorm 2 a very long time ago. I was shocked to see Qor only supports the old version. Gorm 2 has much better support for indexes in Postgres than the previous one, so there is no option of downgrading. What is the status of porting Qor to Gorm 2, and is there perhaps a workaround like force casting the Db object to the correct type which we can do in the meantime? |
Any updates or fork fixes this problem |
Kind of hard to believe that there is no fix yet after 1 year. |
Any updates? |
When I'm trying to use qor with gorm.io/gorm, I got this error
cannot use DB (type *"gorm.io/gorm".DB) as type *"github.com/jinzhu/gorm".DB in field value
how can I deal with this problem?
The text was updated successfully, but these errors were encountered: