comment on

Ever the conservative one, I would go for (2), with (1) being the second choice:

As you put it nicely: we can't have backward incompatible changes. If nobody has complained so far (has anybody complained? I don't see anythink on rt.cpan.org) it probably means that it is not really a problem for users.

I see an other option BTW: (4) (possibly optionaly), internally do a SELECT count(<query>) FROM... to get the info first, then do the query (all nicely wrapped in a transaction I would assume).

Maybe contacting the author of SQLite to get a function that would return the count, before using sqlite_step might also be a good idea, as it would move the extra step out of Perl (and out of your module) and into the core library.

In reply to Re: DBD::SQLite dilemma by mirod
in thread DBD::SQLite dilemma by Matts

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.


more useful options
	PerlMonks