I thought that support for parameters was supplied by the underlying data layer?
For example, in ADO, when you get the parameters for a query, it send the query to the database and which parses it and the sends back a list of types parameters which the client fills in before making the call. I don't think you need to be doing any SQL parsing in the System.Data classes unless the particular data layer that you're providing a connector for doesn't support this feature - but OLEDB & ADO (and JDBC, I think) don't require this. Piers. -----Original Message----- From: Daniel Morgan [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 11, 2002 2:19 AM To: Mono List Subject: [Mono-list] SQL Parser for System.Data Anyone have any experience at creating a SQL parser? How do I create a SQL parser in C#? Or is there an open source (as in X11 free or BSD free) SQL parser already written in C# or Java? I do understand that the Mono C# compiler (mcs) is written in C# and uses jay (a Berkeley yacc parser ported to java ported to C#), but other than that, I have no idea where to begin. I do not understand jay, yacc, nor creating language parsers. However, I do need it for System.Data Parameters support (IDbParameter, SqlParameter, and OleDbParameter). Parameters are used for passing data back and forth between .NET programs and stored procedures. They are also used for prepared SQL commands and queries that must be precompiled so it can be executed multiple times without having to recompile the SQL command. Thanks, Daniel _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
