LarrySteele
Programmer
Background first...
I had a table with fields such as
The desired output was
I searched and found a number of solutions available for v 8.2 and higher using various XML related functions. We have 8.1.5 and sure enough the functions didn't appear to work right.
Since the output was going to Microsoft Access I chose to just let the application concatenate the values. Quick, efficient, and works well.
Now, the question...
On one of the websites I visited, a poster was adamant that data manipulation like this should be handled by the client application, not the db engine.
I've never heard anything like this before and wanted to see what others think - especially DBA's. Should I be concerned with amount of work I put on the db engine versus the amount I put on the client application? If yes, what's a good rule of thumb?
I had a table with fields such as
Code:
PERSON_ID V
0001 A1
0001 A2
0001 A3
0002 A1
0002 B1
0003 A1
0003 A3
0003 B1
The desired output was
Code:
PERSON_ID V
0001 (A1,A2,A3)
0002 (A1,B1)
0003 (A1,A3,B1)
I searched and found a number of solutions available for v 8.2 and higher using various XML related functions. We have 8.1.5 and sure enough the functions didn't appear to work right.
Since the output was going to Microsoft Access I chose to just let the application concatenate the values. Quick, efficient, and works well.
Now, the question...
On one of the websites I visited, a poster was adamant that data manipulation like this should be handled by the client application, not the db engine.
I've never heard anything like this before and wanted to see what others think - especially DBA's. Should I be concerned with amount of work I put on the db engine versus the amount I put on the client application? If yes, what's a good rule of thumb?