On May 5, 10:51 am, ivanb <[email protected]> wrote: > It would be great if Sequel would support ADO.NET, specially now that > IronRuby is out.
There's a fork on github that adds some support for ADO.NET on IronRuby. I've chatted with the author of the fork and he's working on getting it ready for import into Sequel. > Also idea: > I also wonder if now, that there are so many "sub" protocols > (jdbc,dbi,do,ado,odbc,oledb), it would be more logical to separate > connection string to 2 parts, one for DB spec (mysql,postgresql,mssql, > oracle,...) and one for connection (direct,jdbc,odbc,ado, ado.net, > oledb). Not really doable. Internally, Sequel already separates the database specific stuff like SQL syntax from the adapter specific bits. But each adapter needs to at least have some wiring for the databases it supports. For example, you can probably connect to PostgreSQL using the odbc adapter, but there is no wiring in the odbc adapter for PostgreSQL, so you won't get PostgreSQL specific syntax. Also, the do and jdbc adapters just pass the connection string directly, so splitting connection strings wouldn't be possible for those adapters. Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
