riginal Message-
From: sheeri kritzer [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 25, 2006 9:13 AM
To: Brian Menke
Cc: [EMAIL PROTECTED]; mysql@lists.mysql.com
Subject: Re: Fun with Dates and Incentives.
Brian,
MySQL's timestamp function is based on the *server*'s timestamp,
On Wednesday 24 May 2006 15:18, Brian Menke scribble on about:
> Peter, thanks for the detailed info. I will figure out how to get rid of
> the UNIQUE key. Somehow that got added. Thanks for the catch. As far as INT
> for student id goes, I'm using email because it will be unique, and offers
> an e
On Wednesday 24 May 2006 15:18, Brian Menke scribble on about:
> Peter, thanks for the detailed info. I will figure out how to get rid of
> the UNIQUE key. Somehow that got added. Thanks for the catch. As far as INT
> for student id goes, I'm using email because it will be unique, and offers
> an e
kritzer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 25, 2006 9:13 AM
To: Brian Menke
Cc: [EMAIL PROTECTED]; mysql@lists.mysql.com
Subject: Re: Fun with Dates and Incentives.
Brian,
MySQL's timestamp function is based on the *server*'s timestamp, not
the client's.
-Sheeri
On 5/24/0
ROTECTED]
Sent: Thursday, May 25, 2006 9:13 AM
To: Brian Menke
Cc: [EMAIL PROTECTED]; mysql@lists.mysql.com
Subject: Re: Fun with Dates and Incentives.
Brian,
MySQL's timestamp function is based on the *server*'s timestamp, not
the client's.
-Sheeri
On 5/24/06, Brian Menke <
S!
-Brian
_
From: Peter Brawley [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 24, 2006 3:56 PM
To: Brian Menke
Cc: mysql@lists.mysql.com
Subject: Re: Fun with Dates and Incentives.
Brian,
CURRENT_TIMESTAMP gives you time in your server's timezone. UTC_TIMESTAMP
gives GM (univer
_
From: Peter Brawley [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 24, 2006 1:31 PM
To: Brian Menke
Cc: mysql@lists.mysql.com
Subject: Re: Fun with Dates and Incentives.
Brian
Re your schema,
--it's redundant to define PRIMARY and UNIQUE keys on the same column,
-
awley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May
24, 2006 1:31
PM
To: Brian Menke
Cc:
mysql@lists.mysql.com
Subject: Re: Fun with
Dates and
Incentives.
Brian
Re your schema,
--it's redundant to define PRIMARY and UNIQUE keys on the same column,
--why not an INT
Brian,
Somehow the server ate my response...
Re your schema,
--it's redundant to define PRIMARY and UNIQUE keys on the same column,
--why not an INT student id?
--what if two (eg married) students share an email account?
--comparing datetimes across multiple time zones will be simpler if you
ian
_
From: Peter Brawley [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 24, 2006 1:31 PM
To: Brian Menke
Cc: mysql@lists.mysql.com
Subject: Re: Fun with Dates and Incentives.
Brian
Re your schema,
--it's redundant to define PRIMARY and UNIQUE keys on the same column,
--why not
Brian
Re your schema,
--it's redundant to define PRIMARY and UNIQUE keys on the same column,
--why not an INT student id?
--what if two (eg married) students share an email account?
--comparing datetimes across multiple time zones will be simpler if
you
set completed_modules.tim
I think doing a sort by date with limit 10 should get you the first
ten. I believe the now() function uses the server time, so no need to
do date/time calcs really.
Good luck,
Jason
Brian Menke wrote:
I'm hoping for some general advice on an approach for the following
scenario:
I have a
TECTED]
> Sent: Wednesday, May 24, 2006 12:51 PM
> To: mysql@lists.mysql.com
> Subject: Fun with Dates and Incentives.
>
> I'm hoping for some general advice on an approach for the following
> scenario:
>
>
>
> I have a customer who wants to put an incenti
I'm hoping for some general advice on an approach for the following
scenario:
I have a customer who wants to put an incentive program in place for
students taking learning modules and then completing tests. The concept is
simple. Award the first 10 people who complete a test with a score of
100
14 matches
Mail list logo
