I'm having the issue with CREATE TABLE described by Bug #30513 (http://bugs.mysql.com/bug.php?id=30513
). To summarize, a table which previously existed, and then is dropped
by DROP TABLE IF EXISTS, becomes randomly unable to be recreated. Here
is my comment on that bug:
Having this same
Off the top of my head I can't think of a way of getting the output in
the format that you want.
If you use a query like:
SELECT SUBSTRING(sales_date,1,10), sales_type, COUNT(sales_id)
FROM sales_activity
GROUP BY SUBSTRING(sales_date,1,10), sales_type;
You'll get output like:
Date
Hi,
Here is the simplest test case I could boil this down to. I'm running
this in 5.0.51a on RHEL4.
Preconditions:
- mysql.user only contains root user
- mysql.db is empty
- mysql.tables_priv is empty
- mysql.host is empty
I login as root, and run the following:
CREATE TABLE test.foo (
My first impression is to say: Sounds like the InnoDB internal data dictionary
still has the table recorded somewhere. According to Page 566 Paragraph 3 of
MySQL Administrator's Guide and Language Reference (ISBN 0-672-32870-4),
InnoDB always needs the shared tablespace because it puts its
On Jun 24, 2008, at 10:13 AM, Rolando Edwards wrote:
My first impression is to say: Sounds like the InnoDB internal data
dictionary still has the table recorded somewhere. According to
Page 566 Paragraph 3 of MySQL Administrator's Guide and Language
Reference (ISBN 0-672-32870-4),
InnoDB
On Thu, Apr 24, 2008 at 4:06 PM, Rob Wultsch [EMAIL PROTECTED] wrote:
I have been storing points in mysql without use of the spatial
extension. I do not forsee the need to ever store more than points,
and am wondering if the spatial extensions would offer any significant
advantages. I have
Hi guys,
This might be somewhat off topic but does anyone have experience with Baron
Schwartz's maatkit, particulary with error messages?
I have several databases on my master/slave setup and can use
mk-table-checksum on almost all of them on both hosts.
There are 3 databases where I get this
In mysql, GROUP BY also by default does sorting using ORDER BY, so you an
avoid it by including ORDER BY NULL after GROUP BY, this should help.
On 6/24/08, Jerry Schwartz [EMAIL PROTECTED] wrote:
sigh In all of that information, I forgot to post the actual query:
INSERT INTO
Hello,
I have a Company table with 50 million rows that I am trying to index
with Hibernate search with
fullTextSession.setFlushMode(FlushMode.MANUAL);
fullTextSession.setCacheMode(CacheMode.IGNORE);
ScrollableResults results = fullTextSession.createCriteria(
Company.class
