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 methods to batch insert and delete records from Tableview #121
Comments
It might make sense to expose the |
One option would be to start the application with the treeview with empty rows, and let the user do the sql query outside the widget. And the result of this sql query will be inserted into the treeview. So the user could do as many queries as they want, and the data would be erased and inserted into the treeview at runtime. I tried to do something like this, I made some changes I don't know if it generates bad consequences.
My custom sql search button: Externally to the widget I now do this to delete all rows: or like this:
clear the rowcount: '_tablerows' I think I would need to make an attribute public. I do my sql query and inject the result in treeview: I update the data and do the autofit, reset sort header
https://www.mediafire.com/file/g95y9yjsuz5tzew/datable_mod.mp4/file When there is something typed in the custom filter field, it makes another sql query (example from the video: returns the entire database table in descending order.) Do these adjustments that I made generate any conflicts in the rest of the widget's code? |
In addition to the possibility of inserting or deleting lines. A method to update rows would be interesting. For example, The line information would be loaded into an external form. The user changes the necessary data and updates this new data in the indicated row of the treeview. |
I think I can make a small tweak to some things I added in the recent PR and get this to work pretty smoothly on updates... You can get the TableRow object via looking it up via the |
One note though... using the syntax |
This is possible with the underlying Tableview.view (Treeview), but this api really needs to be exposed with easy to use methods. See this post for a use case.
The text was updated successfully, but these errors were encountered: