-
ekerin committed patchset 6 of module java_client to the Open Robotics Peripheral Platform CVS repository, changing 12 files.
2005-05-01 23:37:22 UTC in Open Robotics Peripheral Platform
-
ekerin committed patchset 5 of module java_client to the Open Robotics Peripheral Platform CVS repository, changing 1 files.
2005-05-01 03:30:33 UTC in Open Robotics Peripheral Platform
-
ekerin committed patchset 4 of module java_client to the Open Robotics Peripheral Platform CVS repository, changing 5 files.
2005-05-01 03:29:51 UTC in Open Robotics Peripheral Platform
-
ekerin committed patchset 3 of module java_client to the Open Robotics Peripheral Platform CVS repository, changing 2 files.
2005-04-30 06:26:29 UTC in Open Robotics Peripheral Platform
-
ekerin committed patchset 2 of module java_client to the Open Robotics Peripheral Platform CVS repository, changing 1 files.
2005-04-30 06:25:20 UTC in Open Robotics Peripheral Platform
-
ekerin committed patchset 1 of module java_client to the Open Robotics Peripheral Platform CVS repository, changing 13 files.
2005-04-28 05:28:42 UTC in Open Robotics Peripheral Platform
-
yea, basically, Lookup in the user table for the email address that was entered, if it dosn't find it, "Avast, we've never heard of ye." If it does, it sends the mail.
2004-01-15 14:14:20 UTC in phpMyPirates
-
I saw this method before, I think it works pretty good.
1. User clicks on the link for I lost my password
2. It explains the process, enter their username/email, and hit ok.
2. A key is generated, saved, and e-mailed to the user at the address they registered as a link.
3. The user navigates to that link, and it then allows them to set a new password.
Sound good? I'll code it up if you...
2004-01-15 02:18:28 UTC in phpMyPirates
-
ekerin committed patchset 40 of module phpmypirates to the phpMyPirates CVS repository, changing 1 files.
2004-01-03 02:06:38 UTC in phpMyPirates
-
The technically correct way is to have the information in one place and only one. But sometimes you break that rule in the name of speed.
The problem you're running into is caused my MySQL's sub-par implementation of SQL. In this case it lacks subselects.
This would be the way I would write it, given subselects:
SELECT
promotion.pirate,
promotion.rank
FROM
promotion,
2004-01-03 01:46:03 UTC in phpMyPirates
