The second solution also has the benefit of not actually touching the existing codebase. But, as someone who's done this kind of work (GL -> OpenGL), it's not as easy as it sounds.
Problems you will encounter:
- There isn't a 1-1 mapping between functions in the old and functions in the new.
- You'll probably have to write a bunch of state maintenance.
- Testing this will be absolutely imperative.
You might find it easier to take the existing Postgres module and rewriting its
calls to use DBI
. That way you know you have every possible call to Postgres covered and you don't have to worry about state maintenance and the like. Remember - all you have to change is the communication with the DB - the external stuff. You do not (and should not) have to change how Postgres works, internally. In fact, keeping it the same will improve your success potential.
We are the carpenters and bricklayers of the Information Age.
Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.
Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.