https://bugs.freedesktop.org/show_bug.cgi?id=83171
--- Comment #4 from Doug <[email protected]> --- Swapping the under-the-hood functionality with views might address this problem and relieve pressure on Base development. I assumed that LO under-the-hood did something like create a view, meaning a second query using the first would remain simple. Had not been using LO for table management, didn't explore LO's 'view' support. Seems redundant most of the time to have both saved queries and views in the same app; I assumed that part of the reason for back ends to support "views" was to provide native saved-query-type functionality that Access and LO provide through the query manager. Seems LO would need one or other, but in most cases, not both. LO GUI query editor doesn't support subqueries anyway (a limitation for views in MySQL at least), and anyone intrepid enough to write complex query in the LO SQL direct editor could save those in the way LO does now, outside of views. Using views instead of queries seems to be a best practice on the user's end, making pseusdo-tables available on the back-end and for the reasons you describe. If you were coding LO from scratch, seems natural that nearly all queries would be 'views'. LO 'view' support already seems mature; swapping in user support would involve largely aesthetic changes. You could classify that as an enhancement request, and it is so natural that I'll bet it already is on a list somewhere. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
