Also, how easy will it be to overload/hook into the SQL syntax processing ? I've been hacking something similar for an ETL app to permit INSERT...SELECT.../UPDATE...FROM (and an UPSERT with both) for large scale data movement, but in some instances it requires multiple connections per data source...I'd love to exploit your stuff if there's some simple method for overloading...
And just to make sure I understand...will an INSERT SELECT/UPDATE FROM be able to embed callbacks as "pseudo tables" ala: INSERT INTO [EMAIL PROTECTED] SELECT my_filter_funcion(*) FROM (SELECT * FROM [EMAIL PROTECTED]) db2table; sub my_filter_function { my @params = @_; .... return @row; } I *think* your msg indicates such support, but perhaps I misinterpretted ? Dean Arnold Presicient Corp.