Richard a écrit :
Hello, I'm in the process of programming a customer area with a list
of subscriptions :
Reference | Title | Type | Date of first subscription | Expires
Each item in this list will have a link to it's details with will show
a list like this :
Subscribed on : date of first
Richard a écrit :
Richard a écrit :
Hello, I'm in the process of programming a customer area with a list
of subscriptions :
Reference | Title | Type | Date of first subscription | Expires
Each item in this list will have a link to it's details with will
show a list like this :
Subscribed
Hello, I'm in the process of programming a customer area with a list of
subscriptions :
Reference | Title | Type | Date of first subscription | Expires
Each item in this list will have a link to it's details with will show a
list like this :
Subscribed on : date of first subscription
, otherwise create one in one query.
- Original Message - From: Eric Bergen [EMAIL PROTECTED]
To: Jim McAtee [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, December 04, 2004 2:40 PM
Subject: Re: More efficient way?
Depending on how your application works you might be able to batch
Depending on how your application works you might be able to batch the
daily updates. Example only do an update every 20 items instead of for
each one. Alternatly you could run an update with a join every 10
minutes or so that would update the daily counter.
On Thu, 2 Dec 2004 20:56:45 -0700,
record if
found, otherwise create one in one query.
- Original Message -
From: Eric Bergen [EMAIL PROTECTED]
To: Jim McAtee [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, December 04, 2004 2:40 PM
Subject: Re: More efficient way?
Depending on how your application works you might
I have an application which keeps a table of daily event counters related
to other records in a databse. Since the trackingrecords are kept on a
daily basis new records are created each day for items being referenced.
In pseudo-code:
// Check for the existance of daily tracking record
SELECT
I need to store huge data series using MySQL with InnoDB as storage
engine. The data type of the parameters can be double, float, int,
smallint, mediumint, tinyint So, I've thought to store them in
the following way:
Table Parameter:
Parameter ID - small int
Parameter Name - varchar(8)
Hello,
If you aim for for absolute control over the storage (the fileystem
nature is the limit), and speed, do not use an SQL system. Of course,
you would have to face all the trouble of writing your own
mini-engine/subsystem for the job. It all comes down to what your
needs are and how much
