It is not a superset of the existing SQLTransformer. We tried to implement as many features of the existing one as possible, but really focused on the features we needed at the time. Also, it would not be backwards compatible, as the XML driving it is different. So, I don't think it could replace it, it would probably make sense to have this be an additional transformer.

We have many examples of how to use it, but a lot of them are fairly customer specific. So, I could send some of them to you, but would flag the ones that you cannot share. (Maybe you could just change the table names or something like that) I do have a small project we worked on that I could share the code for that.

I assume the next steps would be for us to zip up the code and the examples and send them along? Does that sound like a plan? Also, I assume I would just send them directly to you instead of hitting the whole list with them.

Let me know how you'd like me to proceed.

Irv

Bertrand Delacretaz wrote:

Hi Irving,

Your alternate SQL transformer looks interesting to me. If we'd like to add it to the project, what do you suggest? Is it compatible enough with the existing one to replace it, or should it rather be a different "advanced SQL transformer" or something?

Also, would you be able to provide samples of its use, that we could add along with the component?

I don't know if you're aware of the discussions about unifying ESQL and the SQLTransformer (there's some info at http://wiki.cocoondev.org/Wiki.jsp? page=UnifiedSQLTransformerAndLogicsheet), but maybe your transformer could be a step in this direction.

-Bertrand



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to