Connecting Tech Pros Worldwide Forums | Help | Site Map

SELECTing multiple rows to a single output line

R. P.
Guest
 
Posts: n/a
#1: Aug 14 '05
Anybody knows a way to produce output from a SELECT statement on a
single line, instead of each hit on a separate line?

Here is what I mean: let's say I have a table listing families, one per
row that includes the name of father, mother and the number of children.
Then there would be another table with one row for each child and the
rows would be linked to the first table with a foreign key scheme.

Now I would like to list each family with joining the two tables, with
the name of children listed on the same line as the parents, with --
say -- a comma separating each child's name.

I can't figure out any way to produce SELECT output serially, on a
single line. Some suggested stored procedures but my past experience
with stored procedures was that they often were "unstored" when the DBA
did some maintenance and it was just not as reliable as using dynamic
SQL statements, in this case with Java.

Thanks for any tips you might have,
Rudy



Guest
 
Posts: n/a
#2: Aug 16 '05

re: SELECTing multiple rows to a single output line



"R. P." <r_pol12gar@hotmail.com> wrote in message
news:0v-dnc7yieg3XmPfRVn-2Q@comcast.com...
| Anybody knows a way to produce output from a SELECT statement on a
| single line, instead of each hit on a separate line?
|
| Here is what I mean: let's say I have a table listing families, one per
| row that includes the name of father, mother and the number of children.
| Then there would be another table with one row for each child and the
| rows would be linked to the first table with a foreign key scheme.
|
| Now I would like to list each family with joining the two tables, with
| the name of children listed on the same line as the parents, with --
| say -- a comma separating each child's name.
|
| I can't figure out any way to produce SELECT output serially, on a
| single line. Some suggested stored procedures but my past experience
| with stored procedures was that they often were "unstored" when the DBA
| did some maintenance and it was just not as reliable as using dynamic
| SQL statements, in this case with Java.

http://builder.com.com/5100-6388_14-5259821.html


Closed Thread