Hi Kevin,
On Sat, Feb 5, 2011 at 6:00 AM, Kevin Spencer wrote:
> When you use a leading wildcard symbol, MySQL will do a full table
> scan regardless of any indexes you've created.
>
Is it also apply to regex lookup ?
Regards,
Feris
Hi Johan,
On Sun, Dec 19, 2010 at 7:11 PM, Johan De Meersman wrote:
> You can't query the index directly, but if you select only fields that are
> in the index, no table lookups will be performed - this is called a covering
> index.
>
Great.. Thanks for the confirmation.
Regards,
Feris
>
> -
Hi Everyone,
Is there a way to query values stored in our index instead of using "group
by" selection which will produce same results ?
Please advice..
Regards,
Feris
Hi Johan,
On Thu, Dec 16, 2010 at 4:03 PM, Johan De Meersman wrote:
> Hmm, interesting. What does this do, exactly ? Can something similar be
> applied to non-jdbc connections, too ?
>
I'm not quite sure... but will try to trace it. Will ask this in another
thread.
FYI, when I try it using FIF
Hi Mark,
On Thu, Dec 16, 2010 at 4:50 AM, Mark Matthews
wrote:
> Feris,
>
> I don't know what Kettle is doing under the hood, but if it's doing
> addBatch(), executeBatch(), then adding "rewriteBatchedStatements=true" to
> your MySQL JDBC URL should probably help quite a bit.
>
It works. By ha
Hi Mark,
On Wed, Dec 15, 2010 at 8:10 AM, Mark Matthews wrote:
> Feris,
>
> *How* are you writing, via batch statements with rewriting, or directly, or
> via LOAD DATA INFILE? It seems you're off by about a factor of 10-20x from
> what I've seen performance-wise for writes.
>
I'm using ETL mean
Hi All,
I have a data warehouse infrastructure with following configuration :
- MySQL 5.0 MyISAM + InndoDB enabled (XAMPP Distribution)
- Windows 2003 64 bit data center edition
- Java Runtime 6 - 32 bit version
And have ETL running data warehouse process. Reading is impressive, 12,000
rows per s
Hi Martin,
You are correct. That's the same error that I got.
Looks like this article is the solution =>
http://dev.mysql.com/doc/refman/5.1/en/innodb-backup.html
Thanks !
Feris
On 1/31/08, Martijn Tonies <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > > By default, InnoDB tables aren't stored in the d
Message
> > Date: Thursday, January 31, 2008 09:00:38 PM +0700
> > From: Feris Thia <[EMAIL PROTECTED]>
> > To: mysql@lists.mysql.com
> > Subject: Data folder copying problem
> >
> > Hi all,
> >
> > I have 2 database folder that being cop
Hi Martin,
On 1/31/08, Martijn Tonies <[EMAIL PROTECTED]> wrote:
> Hi,
>
> By default, InnoDB tables aren't stored in the database folder, but rather
> in it's own table space files.
>
In fact when I try to drop the database, the server "recognizes"
innodb tables. For example, T1 and T2 are INNOD
Hi all,
I have 2 database folder that being copied directly from a remote
server and sent to me. That databases contains both MYISAM and INNODB
tables.
After I received the data, I try to restored it by copying that
folders to my server. The problem is, only MYISAM tables are being
recognized. Ho
11 matches
Mail list logo