Re: Using the result of a function as a column name.
- From: "Uri Dimant" <urid@xxxxxxxxxxx>
- Date: Thu, 29 Oct 2009 09:50:52 +0200
Why not? Fixed length names are easier to put on a report or screen,
to write check() constraints for, etc.
What report? What screen?
format ('2009-Q1' instead of '2009-Fiscal_1') but it is an entity
would have to maintain its identity (in the sense of logical
identity).
Not sure what you meant by the above.
I just want to as, have you ever worked on OLTP with high concurent number
of transactions? Are you aware that having wide CI may hurt performance ,
not talking about disk space and maintenance....
"--CELKO--" <jcelko212@xxxxxxxxxxxxx> wrote in message
news:9316629f-a345-4bcb-aca2-581c8cbe9f64@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
But why using CHAR(15) instead of VARCHAR(15)? <<
Why not? Fixed length names are easier to put on a report or screen,
to write check() constraints for, etc. But the point is that this was
a skeleton and that was just a number; in a real schema, the length
would be determined by some internal group (probably accounting or
marketing) and so would the CHECK() constraint.
What if I want to change the name of report later on do you think you
did not produce a fragmentation? What if during a transaction JOIN ON
period_name you change the name of report? <<
You are being absurd. First of all, what new names would you give the
first fiscal quarter of 2009? I might change my name to a different
format ('2009-Q1' instead of '2009-Fiscal_1') but it is an entity
would have to maintain its identity (in the sense of logical
identity). Next, reporting periods are usually fixed by law; or if
they are historical, th4ey are fixed by reality (i.e. I cannot change
Ramadan 2000 to anything else). But let's keep being silly -- What if
I want to change the value of pi in a look up table?
.
- References:
- Using the result of a function as a column name.
- From: Jason R. Soby
- Re: Using the result of a function as a column name.
- From: --CELKO--
- Re: Using the result of a function as a column name.
- From: Uri Dimant
- Re: Using the result of a function as a column name.
- From: --CELKO--
- Re: Using the result of a function as a column name.
- From: Uri Dimant
- Re: Using the result of a function as a column name.
- From: --CELKO--
- Re: Using the result of a function as a column name.
- From: Uri Dimant
- Re: Using the result of a function as a column name.
- From: --CELKO--
- Using the result of a function as a column name.
- Prev by Date: SQL Server Import CSV data and skip duplicate rows
- Next by Date: CPU utilization reached to 100%
- Previous by thread: Re: Using the result of a function as a column name.
- Next by thread: Re: Using the result of a function as a column name.
- Index(es):
Relevant Pages
|