On 04-06-2011 01:16, Darren Duncan wrote:
b. That's just an example of how MySQL silently ignores lots of errors or
silently changes data on you, such as silently truncating text values that
are
too long for a field when you insert them, so you've lost data without even
knowing it.
Hi,
First, think you for doing sqlite. I like it !
I am surprised by the result of EXPLAIN QUERY PLAN on some queries.
I will explain try to explain my issue.
1-Open the attached database
This database contains a table a:
CREATE TABLE a(id INT,v REAL,r_a_id INT)
Thank you Igor, I'll do some more thorough profiling.
When I run the query:
UPDATE multiturnTable SET complete=1 WHERE id=-5
This takes ~45ms (as reported by SQLite's profile) - is this in the
right ballpark? I'm running a fairly fast modern intel chip here.
Thanks,
Ian
2011/6/3 Stéphane MANKOWSKI steph...@mankowski.fr
4-EXPLAIN QUERY PLAN SELECT total, total+1, total+2 FROM v_c
returns:
SCAN TABLE c (~74 rows)
EXECUTE CORRELATED SCALAR SUBQUERY 1
SEARCH TABLE a USING INDEX a_r_a_id (r_a_id=?) (~88 rows)
EXECUTE CORRELATED
On 03-06-2011 14:29, Stéphane MANKOWSKI wrote:
Hi,
First, think you for doing sqlite. I like it !
I am surprised by the result of EXPLAIN QUERY PLAN on some queries.
I will explain try to explain my issue.
1-Open the attached database
This database contains a table a:
This is an auto-replied message. I am out of office right now, with no access
to e-mail.
I will be returning on Monday, 13 June.
If you need Berkeley DB assistance before then, please use My Oracle Support or
the Oracle Berkeley DB Forums. For urgent issues, please contact Adam Whitter
at
On 03/06/2011, at 11:40 PM, Ian Hardingham wrote:
Hey guys, thank you very much for the help so far.
The list of calls which I make during the end match section, which can
take 2 seconds, is:
SELECT * FROM multiturnTable WHERE id=? LIMIT 1
UPDATE multiturnTable SET p1SubmitScore=1
On Jun 3, 2011, at 6:16 PM, Darren Duncan wrote:
Mr. Puneet Kishor wrote:
On Jun 3, 2011, at 1:19 PM, Darren Duncan wrote:
MySQL should be avoided like the plague.
why?
This is a long standing (un)conventional wisdom to which I too have hewed.
Now, it so happens, I will be starting work on
Tom, thank you so much for the extensive advice.
Ian
On 04/06/2011 15:27, BareFeetWare wrote:
On 03/06/2011, at 11:40 PM, Ian Hardingham wrote:
Hey guys, thank you very much for the help so far.
The list of calls which I make during the end match section, which can
take 2 seconds, is:
Mr. Puneet Kishor wrote:
On Jun 3, 2011, at 6:16 PM, Darren Duncan wrote:
a. MySQL silently ignores all CHECK constraints in all engines, so for
example you can't even tell it you want a column to only hold values
between 1 and 10. Its in the MySQL docs: The CHECK clause is parsed but
10 matches
Mail list logo