to intercept and act upon SQL strings, I would look into ConnectionProxy: http://www.sqlalchemy.org/docs/reference/sqlalchemy/interfaces.html?highlight=connectionproxy#sqlalchemy.interfaces.ConnectionProxy
otherwise, if its a mediating layer to a DBAPI that is supported by SQLA, you could make a wrapper around it and pass it to create_engine() using the "module" argument. On May 28, 2010, at 2:12 AM, Paul Hemans wrote: > I am very new to SA and I need to create a dialect for a legacy db on > windows. The problem is that the resulting SQL strings need to pass > into another application to be actioned. That is, not through any sort > of ODBC/OLEDB... connector. > So the way I see it, I have a few issues to deal with. Create a > dialect, trap the generated SQL strings, action them and return a > result set to SA. Don't mind the work but I wouldn't know where to > begin, so if anyone could give me some pointers that would be great. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@googlegroups.com. > To unsubscribe from this group, send email to > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
