On May 10, 10:53 am, ivanb <[email protected]> wrote: > On May 5, 8:22 pm, Jeremy Evans <[email protected]> wrote: > > 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. > > Hm, I was thinking about this scenario, for example: > When you insert a row in oracle, you tipically get autonumber from > sequence. > When you insert a row in informix, you execute some sql to get this > number. > So "method" to get last row is not "transport" (odbc,jdbc,ado.net) > specific, is db-specific.
It's actually tied to a combination of the the adapter and database. For example, the ADO MSSQL subadapter handles it differently than the ODBC MSSQL subadapter. This is another reason you can't completely separate the database support from the adapter support. Sequel has three types of adapters: 1) Main adapters: what you specify when connecting (ado, postgres, odbc, etc.) 2) Shared adapters: containing specific database support (mssql, postgres, mysql, etc.) 3) Sub adapters: Tying the main adapter to the shared adapter, and adding specific support to the combination (mssql on ado, postgresql on jdbc, etc.) Hopefully that helps clear things up. 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.
