It would be great if Sequel would support ADO.NET, specially now that IronRuby is out.
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). So one would say, connect via jdbc to mysq. or Connect to oracle via ado.net -- 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.
