I really understand [the need for prepare_cached()], and I can see that an application would want to use it, but Sybase's support of placeholders is (maybe) somewhat limited in this respect.
Sometimes abstractions work great in theory, but suck for some edge cases. Trying to pretend that all databases support placeholders makes code much more portable, at the expense of suboptimal (or just plain terrible) performance when dealing with a database that doesn't support placeholders. Sybase, at least through the native DB*Lib API, doesn't support placeholders (I think this is true through CT*Lib, though that's years back, and I don't have that API at hand). To cope with this, the various abstract APIs (e.g., DBI, ODBC) that sit atop the native API have to pretend to prepare a query while in reality they're expanding the query and quoting bind variables at execute time.
-
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.
|
