;Gary Richardson" <[EMAIL PROTECTED]>
To: "Phil Bitis" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, October 21, 2004 2:45 AM
Subject: Re: B-tree index question
If you are using MyISAM tables, have you thought about using MERGE
tables instead? You could
From: "Sergei Golubchik" <[EMAIL PROTECTED]>
But for auto_increment field (on BIGINT, I believe ?),
you'll have hundreds of keys on one key page, so logarithm base will be
few hundreds, and log N should be just 3-5. That is, it should be only
~3-5 times slower as compared to the table with one hund
ssage -
From: "Sergei Golubchik" <[EMAIL PROTECTED]>
To: "Phil Bitis" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, October 20, 2004 9:23 AM
Subject: Re: B-tree index question
Hi!
On Oct 23, Phil Bitis wrote:
Hello,
We want to be able to inser
Thanks for the reply. We're actually using DELAY_KEY_WRITE on our tables.
The manual says (7.2.15):
Declaring a MyISAM table with the DELAY_KEY_WRITE=1 table option makes
index updates faster because they are not flushed to disk until the table is
closed.
Does this work with all types of indexe
Hello,
We want to be able to insert records into a table containing a billion records in a
timely fashion.
The table has one primary key, which I understand is implemented using B-trees,
causing insertion to slow by log N.
The key field is an auto_increment field.
The table is never joined to ot
CREATE TABLE tbllayer (
LayerID int(11) NOT NULL default '0',
LayerSize int(11) NOT NULL default '0',
IceTypeID int(11) NOT NULL default '0',
Fingerprint char(16) binary default NULL,
PRIMARY KEY (LayerID),
UNIQUE KEY Fingerprint (Fingerprint),
KEY IceTypeID (IceTypeID)
) TYPE=MyISAM
For what it's worth, I get the same problem with 4.0.13, and have posted the
same question a few times with no response.
It works fine at the command line, but not through the mysql++ API.
It doesn't work on my home/work machines (both running XP), though my
colleague doesn't experience the problem
Does your university have a webpage indicating what advice is acceptable and
not considered plagarism?
- Original Message -
From: "Antonio Jose Rodrigues Neto" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, July 22, 2003 9:54 PM
Subj
I've been having the same problem, using mysql++ with mysql 4.0.13.
It works just fine entered into mysql-front or mysql.exe, but not through
mysql++
Can I check the CREATE TEMPORARY TABLES privilege through the API?
- Original Message -
From: "Victoria Reznichenko" <[EMAIL PROTECTED]>
To:
Yeah, put LIMIT 20 on the end.
- Original Message -
From: "Jim McAtee" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 14, 2003 11:12 PM
Subject: SELECT TOP
> What's wrong with the following query? The application used to use Access
via
> ODBC, now running MySQL 3.23.xx,
Might it be worth looking at the mailing list manager software for this
list? ACCU's mailing lists use Majordomo and add this line to the rfc822
headers:
Reply-To: [EMAIL PROTECTED]
You can still see the sender's email address if you want to reply directly.
--
MySQL General Mailing List
For l
Is there a limit to the number of records I can insert in a multiple-value
insert?
- Original Message -
From: "Rudy Metzger" <[EMAIL PROTECTED]>
To: "Phil Bitis" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, July 14, 2003 10:18 AM
Subject:
Hiya. I take it you mean ancestors rather than descendants.
For finding descendants I've been using tables like this:
ID ParentIDLineage
1000/100
101100/100/101
102100/100/102
103101/100/101/103
104103/10
Presumably if you don't specify a display size it defaults to the maximum.
I'm just quoting from the manual, have a look at "6.2 Column Types"
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Phil Bitis" <[EMAIL PROTECTED]>; <[EMAIL PR
int(1) takes up 4 bytes worth of space, and just displays 1 character.
BIT or TINYINT(1) take up 1 byte.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 13, 2003 6:05 PM
Subject: Re: does mySQL support a boolean data type?
why don't you use int(1
You can use "BIT" or "BOOL", but these are currently just synonyms for
TINYINT(1). Still your best bet though.
The manual says under new features planned for 5.1: "Optimise BIT type to
take 1 bit (now BIT takes 1 char)"
- Original Message -
From: "Dan Anderson" <[EMAIL PROTECTED]>
To: <[E
Hello,
We've got an application which does many multiple-value inserts to different
tables.
Is it worth locking a table before doing a multiple-value insert with say 50
records? If so, what is the number of records that makes it worthwhile?
If not, is it worth locking a table before doing 2 seper
> > Further to this, I should point out everything works fine in mysql-front
> > or at the mysql console.
> >
> > The problem shows up when using mysql++, a BadQuery exception is thrown.
> >
> > query.reset();
> > query << "CREATE TEMPORARY TABLE " << sTemporary << " TYPE=HEAP
> >
; " TYPE=HEAP
MAX_ROWS=1 " << subselect;
try
{
query.parse();
query.execute();
}
----- Original Message -
From: "Phil Bitis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 09, 2003 12:41 PM
Subj
As a way of getting around the lack of subselect (I'm aware this is coming
soon) we're parsing sql queries, running subselects and storing their
results in a temporary table and replacing the subselect in the sql with the
temporary table name.
This has been working fine, but on upgrading to v4.0.1
20 matches
Mail list logo
