Hi Aaron, I'm not sure if what you want can be done with MySQL, but what you
can do is a little script in python, php, etc, that query your database for
the members that expire at a given date, and then email them. Then you tell
cron o similar to execute your script as often as you require. Hope
Problem is that there are combinations that I'll never care about
What do u mean by the above statement.
I would definitly go for the first solution, though ur taking more time on
the index, but u dont need to keep adding columns and doing joins as u think
would happen in the second approch.
On Mon, Jul 7, 2008 at 2:49 AM, Ananda Kumar [EMAIL PROTECTED] wrote:
Problem is that there are combinations that I'll never care about
What do u mean by the above statement.
What I meant is that I will never do a query for (e.g.) (30, anything).
So I have an index on values that I'll
how many rows would be there in this table and what is the growth rate of
this table.
regards
anandkl
On 7/7/08, Waynn Lue [EMAIL PROTECTED] wrote:
On Mon, Jul 7, 2008 at 2:49 AM, Ananda Kumar [EMAIL PROTECTED] wrote:
Problem is that there are combinations that I'll never care about
What
Waynn Lue wrote:
I have two tables, Applications and Settings. Here are the two schemas:
mysql desc Applications;
+-+-+--+-+-++
| Field | Type| Null | Key | Default |
Extra |
I feel creating the third table would just be duplicating the data and
occupying space. Creating index on existing table and quering would be
better. But you got a good point of FOREIGN KEY CONSTRAINT. Can we use this
constraint on current SETTINGS table, rather than creating the third
table.
On
Ananda Kumar wrote:
I feel creating the third table would just be duplicating the data and
occupying space. Creating index on existing table and quering would be
better. But you got a good point of FOREIGN KEY CONSTRAINT. Can we use this
constraint on current SETTINGS table, rather than creating
Yes, i definitly agree on the third table if APPLICATION FUNCTIONALITY
increase and need to add more columns into the current tables.
On 7/7/08, metastable [EMAIL PROTECTED] wrote:
Ananda Kumar wrote:
I feel creating the third table would just be duplicating the data and
occupying space.
Or, you can use cron/at to schedule the task
Mauricio Tellez wrote:
Hi Aaron, I'm not sure if what you want can be done with MySQL, but what you
can do is a little script in python, php, etc, that query your database for
the members that expire at a given date, and then email them. Then you tell
I run 4.1.20 in master/master for nagios clustering. Everything was
working fine until both machines went down due to power failure in the
IDC. On powering back up one of the machines has come back fine but on
the 'secondary' bearing in mind this is master/master but actually the
01
I know I shouldn't repost, but it's been a week since the last response and
I still don't have a resolution to my problem. In a nutshell, a have an
INSERT query that is taking up over 800mB of file space even though the
tables involved aren't anywhere near that size.
Regards,
Jerry Schwartz
The
This may be done basically by index.php, by running a script in the
background that selects members whose levy is becoming due and have not
already been notified , sends a standard email to the member's email
address and updates a `notification_sent` field with, say, a timestamp
value.
A
Add an autoincrement attribute will make you clear.
On Fri, Jul 4, 2008 at 4:55 PM, Ananda Kumar [EMAIL PROTECTED] wrote:
u mean to says if u have 100 records u want 50 records in one table and
another 50 records in another table?
On 7/4/08, Chandra N [EMAIL PROTECTED] wrote:
Hi,
The biggest difference is that 4.1 does not support store routine but the
5.1 support.
On Sat, Jul 5, 2008 at 1:08 AM, Pablo [EMAIL PROTECTED] wrote:
Hi all,
I'm looking for some information about difference and new features
between mysql 5 and mysql 4.1
Can somebody give me any
14 matches
Mail list logo
