swordfish:

You've already received a mess of good answers, so I won't belabor those points. I'm just going to offer a suggestion: Specifically, don't use '*' as a column list for a SELECT statement. It'll bite you more often than it will help you. The problems are:

• Table changes will change your result sets, often requiring code edits.
• You'll often be reading much more data than you need, increasing network usage.
• You may also be pulling back information you already know (username and password in this case), further impacting network usage.
• You can unnecessarily transmit confidential information that you don't need (again username and password).
• A brief examination of your code won't show you which table columns are in use, making database alteration a bit more difficult.

Generally, request what you need, and only what you need.

...roboticus

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.