On Nov 30, 11:47 pm, "Bernerd Schaefer" <[EMAIL PROTECTED]> wrote:
> I would agree that for now, it's best to stick with do_jdbc.
>
> But going forward -- as we work on the dm-core rewrite -- I would like
> to see DO get upgraded with a JDBC interface, and not the other way
> around. This will also give us the opportunity to build in some
> missing features to DO: prepared statements, blob/clob support, etc.
>
> DO is a great interface, but I can't think of anything we would lose
> by using the JDBC interface for DO, and it would let us use the JDBC
> -without- a wrapper, which to me is -far- better than the alternative.
>
> Bernerd Schaefer
in jdbc:
stm = con.prepareStatement("select name from users where id=?")
stm.setInt(1, 4711)
stm.executeQuery()
in DO:
cmd = con.create_command("select name from users where id=?")
cmd.execute_reader([1])
since DO is almost what prepared statements are for jdbc, it was easy
to use prepared statements for do_jdbc classes.
the only thing I do not understand is what the "new feature" prepared
statements means. what do I miss ?
from what I understand until know I have the feeling switching DO to
mimic/emulate a subset of jdbc would be quite neat.
with regards
Kristian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DataMapper" group.
To post to this group, send email to datamapper@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/datamapper?hl=en
-~----------~----~----~----~------~----~------~--~---
