I see your point and it is valid. Actually, if it were up to me, I'd say beef up ODBC to make it more robust, more able to handle complex data types, aggregates, different call conventions, more detailed error reporting, no-configuration connections, etc., and make that the only database interface. That way we'd separate out two distinct parts:
- how to connect to databases generally from a given programming environment
- how to connect to a given database type
I mean, either that or replace ODBC with something better that accomplishes a similar goal.
Frankly I consider the current system, where each database needs a separate driver for each programming environment, kind of pointless.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
