From: Leonard L. <lle...@ma...> - 2004-03-24 05:19:00
|
I did some quick analysis on the MSysQueries table and from what I could see it did include all of the necessary information (at least on the basic queries that I was trying). I wasn't sure if this was how the queries were handled by jet(3|4) or if they were given there own page in the database (query pages could simply be the data page(s) of the MSysQueries table). I may move forward in trying to use the MSysQueries table since I hit a road block with trying to pull any relevant information from the page returned in entry->table_pg for any given query. Any thoughts on this from the list? I like your idea of porting some of this functionality over to the mdb-sql utility to allow the execution of queries directly. I will keep this in mind as I am working on figuring out exactly how queries work. On Tue, 2004-03-23 at 20:28, br...@br... wrote: > Excellent! I started looking at this probably a year ago and shelved > it to work on other things. Glad to see somebody picking up the > mantle. > > As I recall the MSysQueries table had everything needed except > something (operators?) were stored as enumerated values. Hard to > remember, it's been a while. > > A cool feature along these lines would be to allow queries to be > executed as stored procedures in the SQL engine. So, issuing "exec > myquery" would build a query tree (with or without the intervening > SQL, although certainly with SQL is easier on the first pass) and > execute it. Of course, the mdb-query program is invaluable for > porting to other databases (be carefudQL-dialect specific > language comes up) and as a general tool. |