-
Notifications
You must be signed in to change notification settings - Fork 115
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
add a new filed #125
Comments
Hello, |
sorry, English: |
If I had simply added a new field to register_class like this:
When I execute 'QSqlError daoError = qx::dao::fetch_all(list); 'When I will get an error:
|
“oldfield” is a field in V1.0 and “newfield” is a field that needs to be added in V2.0 |
Hello, When you write : You are using the method qx::QxClass::data which provides other parameters : For example, if you write : And using the QxOrm introspection engine, you can change this property dynamically at runtime (so not in qx_register_class function).
|
Sorry, I described the requirements a bit too complicated, you may have misunderstood my meaning. My current approach is to add the following code snippet, as the new field was added in version 110. Therefore, I determined that when the APP version is less than 110, I will use Alter to add the field. Although this method is feasible, I feel that it is not very elegant, and I think there should be a better way. Looking forward to a reply~
|
Hello, |
I want to add new fields to my new version of the application, how do I set it up to make Qxorm compatible with the new fields?
The text was updated successfully, but these errors were encountered: