comment on

The recordset you retrieve indeed will not contain duplicate records, but that is only because you retrieve more fields and data than you use in your final results.

You do nothing with the second field and you discard all the data after the first ":" delimiter in the third field. And perhaps there are many other fields you do not use at all.

Try to rewrite your SQL so it only gives you exactly what you need.

If that is not possible, then perhaps you should revise your database scheme. If you regularly need the dotted quad as a result, then perhaps that should be a separate field (rather than hidden inside another field) so you can index it and increase the retrieval speed many times.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics

In reply to Re^4: Uniq and sort in perl by CountZero
in thread Uniq and sort in perl by slayedbylucifer

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.


Syntactic Confectionery Delight
	PerlMonks