SQL for field names from a table -- sql server (alternate)

sql server (alternate) : SQL for field names from a table

Dirk Van de moortel
10/6/2005 7:34:54 PM

Hi,

We have a database with some tables with (what I would
denote as) 'referred field names'.
Like this:
DataTable1 with fields F1, F2, F3
DataTable2 with fields F3, F4, F5
DataTable3 with fields F1, F5, F2

We also have a table with field names
FieldNameTable with fields FIELD, NAME
containing data like:
FIELD NAME
----------------
F1 FieldName1
F2 FieldName2
F3 FieldName3
F4 FieldName4
F5 FieldName5

Now, we need a way to query the data of these tables, but
the result of the query should show the 'referred field names'
from the FieldNameTable.

For example, querying DataTable3 should produce the output
FieldName1 FieldName5 FieldName2
------------------------------------------
... ... ...
... ... ...

Any idea how (and whether) this can be done with an SQL query?
Thanks in advance for tips & tricks.

Dirk Vdm

David Portas
10/6/2005 10:39:46 PM

You would have to use dynamic SQL to do that - try and avoid it if you can.
Why not use a view to alias the column names instead of putting them in a
table?

--
David Portas
SQL Server MVP
--

[quoted text, click to view]

Dirk Van de moortel
10/7/2005 6:57:23 AM

[quoted text, click to view]

Ah yes, of course. A few views will do the job just fine.
Thanks.

Dirk Vdm

Dirk Van de moortel
10/8/2005 12:00:00 AM

[quoted text, click to view]

I'm not mixing data and metadata. Someone else did.

[quoted text, click to view]

Trying to make the best of someone else's mess without
interfering ;-)

[quoted text, click to view]

I know.
I will pass the message. In fact I alread have, but they
don't care.

Dirk Vdm

--CELKO--
10/8/2005 9:02:06 AM

Let's get back to the basics of an RDBMS. Rows are not records; fields
are not columns; tables are not files. Then you are mixing data and
metadata in complete violation of the basic princi-les of data
modeling.

What are you trying to do??? If you do not get a valid design, you
will wind up with dynamic SQL, procedural code, IDENTITY columns and
all kinds of other non-SQL nightmares.

--CELKO--
10/8/2005 3:56:18 PM

Sorry about that. Have you updated your resume yet? It is always best
to start looking before the company fails ...

Dirk Van de moortel
10/9/2005 9:41:58 AM

[quoted text, click to view]

No problem.

[quoted text, click to view]

It's not the company I work for, and... I don't think it will
ultimately fail over this particular incovenience. If/when it fails,
we'll probably end up using another company's solution
(probably our own), and I'm sure it will have its own little
inconveniences ;-)

Cheers,
Dirk Vdm

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server (alternate)

View Other Months
January 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007

home · blog · groups

Questions? Comments? Contact the dn