On May 9, 2008, at 6:58 AM, Chris Pirazzi wrote:
Hello,
I _thought_ I knew how InnoDB worked, but due to a recent mysql doc
change, I am no longer sure--the change made the dox significantly
less clear, and potentially code-breaking.
Please can someone tell me the real behavior of InnoDB in t
90% of the time you forgot the ";" on the line before the parse error. if
not then I would need to see the code to help you.
Respectfully,
Ligaya Turmelle
""Nitin Mehta"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
there must be some problem in concatenation of strings and number
there must be some problem in concatenation of strings and number variables. If you
can send the lines, we'll be able to suggest the exact change.
Hope that helps
Nitin
- Original Message -
From: CurlyBraces Technologies ( Pvt ) Ltd
To: [EMAIL PROTECTED]
Sent: Tuesday, Februar
NULL |NULL | NULL | 10627007
| where used |
+---+--+-+--+-+--+--
++
1 row in set (0.00 sec)
mysql>
-Original Message-
From: Tonu Samuel [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 5:33 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
On Wed, 2001-10-31 at 08:52, kmlau wrote:
> hi all,
>
>Let me to introduce somethings first, we use mysql for a logging system
> and take about max 150 000 records hourly. And we need to take a period of
> data for analyzing.
I haven't followed the thread but do you use INSERT DELAYED alread
kmlau wrote:
> I encountered a problem about indexing. I want to add index on timerecord
> field in table gw (shown as below) to speed up query relating with time.
> However, I use explain command (explain select * from gw where timerecord =
> '010902') to analyze the performace. As a resul
