David,
On Tue 2002-12-31 at 06:47:38 -0500, [EMAIL PROTECTED] wrote:
[...]
> Oh, I see... I've been thinking about that, too; I currently use a
> datetime field, but all I really need is a date and an hour. I figure
> with one combined field I can match against -YY-ZZ% but maybe two
> fields
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin, et al --
...and then Benjamin Pflugmann said...
%
% Hi David.
Hi!
%
% On Sun 2002-12-29 at 16:21:56 -0500, [EMAIL PROTECTED] wrote:
% > ...and then Benjamin Pflugmann said...
% [...]
% > No; everything is one hour. Two hours is two boo
Hi David.
On Sun 2002-12-29 at 16:21:56 -0500, [EMAIL PROTECTED] wrote:
> ...and then Benjamin Pflugmann said...
[...]
> No; everything is one hour. Two hours is two bookings.
Ah. Good. That makes the case easier and is exactly the case my last
answer was about.
[...]
> % know beforehand when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin, et al --
...and then Benjamin Pflugmann said...
%
% Hi.
%
% On Sat 2002-12-28 at 08:15:58 -0500, [EMAIL PROTECTED] wrote:
% [...]
% > create table schedule
% > (
% > # ID number
% > id smallint not null default 0 auto_increment
Hi.
On Sat 2002-12-28 at 08:15:58 -0500, [EMAIL PROTECTED] wrote:
[...]
> create table schedule
> (
> # ID number
> id smallint not null default 0 auto_increment primary key ,
> client smallint , # references client.id
> class smallint , # references classtypes.id
> place
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, all --
I have tables for clients, instructors, places (rooms), and classtypes,
and finally a schedule where these come together. I'd like to make sure
that a client isn't being double-scheduled (two classes at once), or an
instructor isn't being
