"Hans Forbrich" <forbrich_at_telusplanet.net> wrote in message
news:3E8FCE58.DA81CCE1_at_telusplanet.net...
> Thomas T wrote:
>
> > How acceptable are one row, one column tables? I've heard of people
storing
> > multiple system variables in two-column, multi-row tables, with column
names
> > such as "parameter_name" and "parameter_value". But is using a one
row/one
> > column table common? Or is it a way that works, but of bad design (like
> > creating multiple public rollback segments in the System tablespace)?
>
> A 1-row, 1-column table is not a bad thing. It tends to look silly, and
many
> purists will argue against it. But, remember the most famous table of all
> "DUAL"!
I won't argue against it, it depends on the design. However if bringing dual
into the conversation be aware of the following (in a play area not a
production system that wuld be silly)
sqlplus /nolog
shutdown
startup nomount
select * from dual;
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
Received on Sun Apr 06 2003 - 15:57:30 CDT
