Re: A CSV or a LIST aggregate function
From: Brian Rice (mail_at_brianrice.com)
Date: 10/05/04
- Previous message: Brian Rice: "Re: A CSV or a LIST aggregate function"
- Maybe in reply to: Brian Rice: "Re: A CSV or a LIST aggregate function"
- Next in thread: Brian Rice: "Re: A CSV or a LIST aggregate function"
- Messages sorted by: [ date ] [ thread ]
Date: 5 Oct 2004 12:56:25 -0700
> A concatenated string implies some order to the elements being concatenated.
> Other aggregates are functions of an unordered set whereas a LIST
> "aggregate" would be a function of an ordered set.
I wouldn't think a 'requirement' would be that the list should be
ordered... I'm not even sure if duplicate values should be eliminated.
> Concatenation is (should be!) a presentational
> function only and doesn't belong in the database tier.
I don't agree... there are instances where I have had to make much
more complicated client side procedural code to handle duplicate
rows... and essentially generate a "list" of items myself on several
different fields... when this type of database query would have
resulted in very simple, or even non-existant, client side code... Now
that's a database that works for me. Right?
- Previous message: Brian Rice: "Re: A CSV or a LIST aggregate function"
- Maybe in reply to: Brian Rice: "Re: A CSV or a LIST aggregate function"
- Next in thread: Brian Rice: "Re: A CSV or a LIST aggregate function"
- Messages sorted by: [ date ] [ thread ]