In principle, using <a href="http://ADO.NET">ADO.NET</a> and a purely managed database driver would eliminate most native <-> managed transitions. So in particular, you shouldn't need to marshal string data back and forth any more. On the other hand, database and network I/O is still much more of a bottleneck than local operations ever could be...<div>
<br></div><div>How well does adodbapi work as a 64-bit process? Does it just automatically use a 64-bit version of ADO?</div><div><div><br></div><div><div class="gmail_quote">On Mon, May 11, 2009 at 8:32 AM, Vernon Cole <span dir="ltr"><<a href="mailto:vernondcole@gmail.com">vernondcole@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Question for the group:<br>
If I were to fork a version of adodbapi which used <a href="http://ado.net" target="_blank">ado.net</a> (rather<br>
than COM ado) ...<br>
1) would it work any better/faster than the existing code on Windows?<br>
2) is there any chance that it would run under MONO on Linux?<br>
<font color="#888888">--<br>
Vernon Cole<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.ironpython.com">Users@lists.ironpython.com</a><br>
<a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" target="_blank">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br>
</font></blockquote></div><br></div></div>