Re: Database naming convention (yet another post of it, but a bit different)
From: stu <smcgouga_at_nospam.co.uk>
Date: Thu, 10 Oct 2002 09:46:06 +0100
Message-ID: <ao3ep1$4rd$2$8302bc10_at_news.demon.co.uk>
etc....
Date: Thu, 10 Oct 2002 09:46:06 +0100
Message-ID: <ao3ep1$4rd$2$8302bc10_at_news.demon.co.uk>
>Especially when it comes to cases where
> we have a table with one row.
Slightly OT but...
Are 1 row tables a good idea for storing settings? I usually set up the
following table(s) to store settings in a database:
Setting(pk) Value pi 3.14159265 maxReportSize 90 case 12
etc....
then another (sometimes I store numeric and text values in the same column)
for text settings:
What are the advantages / disadvantages with this structure compared to a
one row table for storing settings. I realise my design is not normalised
(at all!) but it seems to work well.
Cheers
Stu