public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dave Page <[email protected]>
To: Chander Ganesan <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Kevin Hunter <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: Postgres WWW List <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Subject: Re: [SPAM] Re: Training events policy ... first test case
Date: Sun, 04 Nov 2007 22:28:35 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <200711031703310000@114527600>
	<20071103142105.2d29bc1b@scratch>
	<[email protected]>
	<20071103205146.63a6997c@scratch>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Chander Ganesan wrote:
> I think perhaps not.  We already have course titles...and vendors
> consistently use the same name for their courses.  We could simply take
> the course names, their counts, and when the most recent of any
> particular group of courses (start date) is.  Then list the three most
> recent (in terms of start date) along with a count as to the number of
> times they are offered...
> 
> Like: Upcoming courses:
> 
> PostgreSQL Administration (14 events)
> PostgreSQL Cool Tricks and Stuff (3 events)
> PostgreSQL for Dummies (1 event)
> plus 4 Other events...
> 
> If you can send me some DDL I can write up a sample query...

Well thats not exactly the same as was originally suggested, and in fact
does little more than to force events to be grouped by what could easily
be minor differences in phrasing:

PostgreSQL Administration for Beginners (3 events)
PostgreSQL Administration 101 (5 events)
Getting started with PostgreSQL (2 events)
Beginning PostgreSQL (4 events).

If we want to do something like that it needs to be done properly by
(for example) pre-defining some set categories to ensure we list things
appropriately.

Regards, Dave.

view thread (76+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [SPAM] Re: Training events policy ... first test case
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox