ADD A COLUMN IN SERTAIN POSITIONS:

[lenygold via DBMonster.com]

I have a table FAMILY folowing columns:
SSN,NAME,DOB,AGE,PL_BIRTH,MARITAL_STAT

I would like to add a column GENDER between columns NAME and DOB.
Is posiible wihout Droping table FAMILY?

Thank's in avance.
Leny G.

--
Message posted via DBMonster.com
http://www.dbmonster.com/Uwe/Forums....m-db2/200805/1

[Dave Hughes]

lenygold via DBMonster.com wrote:

I have a table FAMILY folowing columns:
SSN,NAME,DOB,AGE,PL_BIRTH,MARITAL_STAT

I would like to add a column GENDER between columns NAME and DOB.
Is posiible wihout Droping table FAMILY?

Thank's in avance.
Leny G.

No, columns can only be appended to a table. Still, I have to ask: why
do you care what position the column is in? It can only make a
difference to queries utilising the evil SELECT * syntax (or the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax).

If you need a column in a different position it's a lot easier to just
define a view ontop of the table which rearranges the columns, rather
than all the rigmarole associated with recreating it.
Cheers,

Dave.

[Frank Swarbrick]

>>On 5/28/2008 at 9:53 AM, in message
<67******************************@posted.plusnet >, Dave
Hughes<da**@waveform.plus.comwrote:

lenygold via DBMonster.com wrote:

>I have a table FAMILY folowing columns:
SSN,NAME,DOB,AGE,PL_BIRTH,MARITAL_STAT

I would like to add a column GENDER between columns NAME and DOB.
Is posiible wihout Droping table FAMILY?

Thank's in avance.
Leny G.

No, columns can only be appended to a table. Still, I have to ask: why
do you care what position the column is in? It can only make a
difference to queries utilising the evil SELECT * syntax (or the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax).

Can you give an example of "the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax"?
I've never heard of it.

Thanks,
Frank

[jefftyzzer]

On May 28, 1:11 pm, "Frank Swarbrick" <[e-mail]>
wrote:

>On 5/28/2008 at 9:53 AM, in message

<[e-mail] >, Dave

Hughes<[e-mail]:

lenygold via DBMonster.com wrote:

I have a table FAMILY folowing columns:
SSN,NAME,DOB,AGE,PL_BIRTH,MARITAL_STAT

I would like to add a column GENDER between columns NAME and DOB.
Is posiible wihout Droping table FAMILY?

Thank's in avance.
Leny G.

No, columns can only be appended to a table. Still, I have to ask: why
do you care what position the column is in? It can only make a
difference to queries utilising the evil SELECT * syntax (or the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax).

Can you give an example of "the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax"?
I've never heard of it.

Thanks,
Frank

An example of SELECT qualifier.* (the "T.*"):

WITH
T(C1, C2)
AS
(
VALUES
(1,1),
(1,2),
(2,1),
(2,2)
)
SELECT
T.*,
MAX(C2) OVER (PARTITION BY C1) MAX_C2_PER_C1_GRP
FROM
T;

--Jeff

[jefftyzzer]

On May 28, 2:17 pm, jefftyzzer <[e-mail]:

On May 28, 1:11 pm, "Frank Swarbrick" <[e-mail]>
wrote:

>>On 5/28/2008 at 9:53 AM, in message

<[e-mail] >, Dave

Hughes<[e-mail]:

lenygold via DBMonster.com wrote:

>I have a table FAMILY folowing columns:
>SSN,NAME,DOB,AGE,PL_BIRTH,MARITAL_STAT

>I would like to add a column GENDER between columns NAME and DOB.
>Is posiible wihout Droping table FAMILY?

>Thank's in avance.
>Leny G.

No, columns can only be appended to a table. Still, I have to ask: why
do you care what position the column is in? It can only make a
difference to queries utilising the evil SELECT * syntax (or the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax).

Can you give an example of "the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax"?
I've never heard of it.

Thanks,
Frank

An example of SELECT qualifier.* (the "T.*"):

WITH
T(C1, C2)
AS
(
VALUES
(1,1),
(1,2),
(2,1),
(2,2)
)
SELECT
T.*,
MAX(C2) OVER (PARTITION BY C1) MAX_C2_PER_C1_GRP
FROM
T;

--Jeff

Or you could do something like:

SELECT
A.*,
B.C5
FROM
A JOIN B
ON
A.COL = B.COL;

--Jeff

[Frank Swarbrick]

>>On 5/28/2008 at 3:48 PM, in message
<20**********************************@s33g2000pri. googlegroups.com>,
jefftyzzer<je********@sbcglobal.netwrote:

On May 28, 2:17 pm, jefftyzzer <[e-mail]:

>On May 28, 1:11 pm, "Frank Swarbrick" <[e-mail]>
wrote:

>>On 5/28/2008 at 9:53 AM, in message

<[e-mail] >, Dave

Hughes<[e-mail]:
lenygold via DBMonster.com wrote:

>I have a table FAMILY folowing columns:
SSN,NAME,DOB,AGE,PL_BIRTH,MARITAL_STAT

>I would like to add a column GENDER between columns NAME and DOB.
Is posiible wihout Droping table FAMILY?

>Thank's in avance.
Leny G.

No, columns can only be appended to a table. Still, I have to ask:

why

do you care what position the column is in? It can only make a
difference to queries utilising the evil SELECT * syntax (or the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax).

Can you give an example of "the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax"?
I've never heard of it.

Thanks,
Frank

An example of SELECT qualifier.* (the "T.*"):

WITH
T(C1, C2)
AS
(
VALUES
(1,1),
(1,2),
(2,1),
(2,2)
)
SELECT
T.*,
MAX(C2) OVER (PARTITION BY C1) MAX_C2_PER_C1_GRP
FROM
T;

--Jeff

Or you could do something like:

SELECT
A.*,
B.C5
FROM
A JOIN B
ON
A.COL = B.COL;

Now that I understand what it does, why is it any less evil than just '*'?

Is this now less evil?

SELECT T.* FROM T

:-)

Frank

[jefftyzzer]

On May 28, 4:05 pm, "Frank Swarbrick" <[e-mail]>
wrote:

>On 5/28/2008 at 3:48 PM, in message

<[e-mail]>,

jefftyzzer<[e-mail]:

On May 28, 2:17 pm, jefftyzzer <[e-mail]:

On May 28, 1:11 pm, "Frank Swarbrick" <[e-mail]>
wrote:

>>On 5/28/2008 at 9:53 AM, in message

<[e-mail] >, Dave

Hughes<[e-mail]:
lenygold via DBMonster.com wrote:

>I have a table FAMILY folowing columns:
>SSN,NAME,DOB,AGE,PL_BIRTH,MARITAL_STAT

>I would like to add a column GENDER between columns NAME and DOB.
>Is posiible wihout Droping table FAMILY?

>Thank's in avance.
>Leny G.

No, columns can only be appended to a table. Still, I have to ask:

why

do you care what position the column is in? It can only make a
difference to queries utilising the evil SELECT * syntax (or the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax).

Can you give an example of "the
slightly-less-evil-and-sometimes-genuinely-useful SELECT qualifier.*
syntax"?
I've never heard of it.

Thanks,
Frank

An example of SELECT qualifier.* (the "T.*"):

WITH
T(C1, C2)
AS
(
VALUES
(1,1),
(1,2),
(2,1),
(2,2)
)
SELECT
T.*,
MAX(C2) OVER (PARTITION BY C1) MAX_C2_PER_C1_GRP
FROM
T;

--Jeff

Or you could do something like:

SELECT
A.*,
B.C5
FROM
A JOIN B
ON
A.COL = B.COL;

Now that I understand what it does, why is it any less evil than just '*'?

Is this now less evil?

SELECT T.* FROM T

:-)

Frank

I leave the final word on the nefariousness of SELECT * to Dave, but
I'd imagine SELECT QUALIFIER.* is considered less evil than SELECT *
precisely because the former *is* qualified, i.e., it's at least a bit
more targeted than SELECT <all columns from all tables>.

--Jeff

[Frank Swarbrick]

>>On 5/30/2008 at 4:46 PM, in message
<8a******************************@posted.plusnet >, Dave
Hughes<da**@waveform.plus.comwrote:

>
Sorry for taking a while to respond to this, unfortunately this is a
complex subject, one which I suspect I'm barely qualified to be
commenting upon. Still, I'll give it a whirl...

Thank you for the very informative and interesting post. I learned quite a
few useful things from it!

Frank