ginning of
the string, and the results will include all subdomains for the given domain
you're looking for.
Regards,
Gavin Towey
-Original Message-
From: Alexander Kolesen [mailto:kolese...@mail.by]
Sent: Saturday, August 01, 2009 11:10 AM
To: mysql@lists.mysql.com
Subject: Re: Table
Hello.
Your query performs a full table scan, because if you match text with '%...'
wildcard, MySQL can't using index. Try to use external full-text
search engines like Sphinx (http://www.sphinxsearch.com/) or Lucene
(http://lucene.apache.org).
> I have a database that I am (will) be using to tra
I have a database that I am (will) be using to track URL's. The table
structure looks like this:
CREATE TABLE event
(
eid INT UNSIGNED NOT NULL AUTO_INCREMENT,
timestamp INT(10) UNSIGNED NOT NULL DEFAULT 0,
ipINT(10) UNSIGNED NOT NULL DEFAULT 0,
fqdn VARC
On 2/6/07, Yong Lee <[EMAIL PROTECTED]> wrote:
Hi all,
Just wondering how people are dealing with tables that are used for
logging, ie: insert only tables supporting occasional queries used for audit
or event logs.
These tables will keep growing and there is no need to keep them that
large
> Hi all,
>
>
>
> Just wondering how people are dealing with tables that are used for
> logging, ie: insert only tables supporting occasional queries used for
> audit or event logs.
>
> These tables will keep growing and there is no need to keep them that
> large so what is the best strategy in man
Hi all,
Just wondering how people are dealing with tables that are used for logging,
ie: insert only tables supporting occasional queries used for audit or event
logs.
These tables will keep growing and there is no need to keep them that large
so what is the best strategy in managing the data
