Comments on: Database Best Practices

By: Recent Links Tagged With "bulk" - JabberTags

Recent Links Tagged With "bulk" - JabberTags — Mon, 13 Oct 2008 03:34:43 +0000

[...] public links >> bulk Database Best Practices Saved by thelamborghini on Sat 11-10-2008 Stranded bulk carrier freed – News.com.auA BULK carrier [...]

By: panzi

panzi — Sat, 06 Sep 2008 15:13:59 +0000

> Offload tasks like string manipulations, concatenations, row numbering, case conversions, type conversions, etc to the front-end application.

Wouldn’t that lead to a bloated DB design?

By: AzMoo

AzMoo — Tue, 26 Aug 2008 07:12:30 +0000

# Avoid leaking your database design details, such as primary keys.

Can you clarify what you mean by this? Avoid leaking?

By: Ignacio Coloma

Ignacio Coloma — Wed, 20 Aug 2008 20:18:31 +0000

You cannot know for sure the number and order of the columns when you select *. If, say, an unused column gets dropped in the database, your query will fail with the weirdest of errors (like an integer field found of type DATE)

By: mpjw

mpjw — Wed, 20 Aug 2008 01:57:03 +0000

If u need all the columns in your application u can do that, but most of the time only selected fields are necessary. Doing a ‘select *’ will definitely impact network, memory, etc.

By: lostsock

lostsock — Tue, 19 Aug 2008 14:30:54 +0000

Great list, thanks.

I am web developer of about 3 years now and I just have a query about one guideline. Is there any reason you suggest “Do not use SELECT * in your queries, explicitly write the required columns names in the select statement.”?

I have found that using ‘SELECT *’ queries allows me to simply add fields to the database in order to have them accessible to my application without the needs to explicitly add them there too. I have read (can’t remember when or where) that using ‘SELECT *’ is not a performance hit so just wondering why you suggest against its use?

Cheers, Danny.