in reply to Parsing and executing a psuedo-language

Depending on the platforms the other datasource(s) run on, and on how up to date these reports need to be, my instinct would be to replicate all the data into some sort of warehouse (on MySQL if appropriate) and let the users carry on using the syntax they know.

This would seem to be far simpler than the parser you're planning (which seems kind of like re-inventing the ANSI SQL wheel), although I appreciate it may not be appropriate for your environment.

Anyway, good luck with it.
  • Comment on Re: Parsing and executing a psuedo-language

Replies are listed 'Best First'.
Re^2: Parsing and executing a psuedo-language
by suaveant (Parson) on May 25, 2005 at 16:37 UTC
    Well... the parser isn't nearly so complex as SQL... it is only parsing a single statement. In the end they want us to move all our data retrieval to the other department's system. Data warehousing it is basically what we have been doing.

    That and sometimes the data is used so infrequently that it isn't really worth storing it locally and wasting all the space...

    So, in the long run this is the best way, as the other system gets more of the data we need and improves the speed of their system, more and more will be retrieved from them directly. Edit By single statement I mean of course the part that makes up a single column return in an SQL query... so really it is just simple math and function calls, there is a lot more to SQL than that :)

                    - Ant
                    - Some of my best work - (1 2 3)