On Tue, Sep 23, 2008 at 11:13 AM, Olexandr Melnyk <[EMAIL PROTECTED]> wrote:
> On 9/23/08, David Ashley <[EMAIL PROTECTED]> wrote:
>>
>> For example, for the 50 states, a lot of programmers would put this logic
>> in
>> the web script and just store the
On Mon, Sep 22, 2008 at 5:12 PM, Ben A.H. <[EMAIL PROTECTED]> wrote:
>
> There are various other fields that I believe could be handled like this
> for
> a cumulative performance boost. For example: country, state/province,
> gender, industry, occupation, ethnicity, language are all options that
>
On Mon, Sep 22, 2008 at 7:54 AM, Colin Charles <[EMAIL PROTECTED]>wrote:
> Nagaraj S wrote:
>
>> Hi Gurus,
>>
>> Good Day! How to apply mysql bug fixing patches or it is just updating or
>> replacing some code in a c file and recompiling the source?
>>
>
> Depending on how your patch looks like, y
On Wed, Sep 17, 2008 at 11:38 AM, Jeffrey Santos <[EMAIL PROTECTED]>wrote:
> Hi David,
>
> My project involves storing information that could have been gathered from
> wildly different sources. You can think of this part of the database as a
> sort of bibliography for the sources of that informat
On Wed, Sep 17, 2008 at 5:46 AM, Jeffrey Santos <[EMAIL PROTECTED]> wrote:
> I'm not sure if this is the right list to ask such a question; if not, any
> direction as to the appropriate forum would be much appreciated!
>
> This may be a simple question, but I'm still on the early stages of my
> le
On Tue, Sep 16, 2008 at 11:02 AM, Dave M G <[EMAIL PROTECTED]> wrote:
> MySQL List,
>
> I'm going through a post-hard-drive-crash process of reinstalling my whole
> operating system, and MySQL is acting very strange.
>
> I installed it as I always have done, by using Ubuntu's Synaptic Package
> Ma
On Mon, Sep 8, 2008 at 12:47 AM, Dan Nelson <[EMAIL PROTECTED]> wrote:
> In the last episode (Sep 08), Yi Wang said:
> > According to the mysql manual, I changed key_buffer_size from 8M to
> > 512M. But In mysql administrator, key buffer hitrate seems stay
> > unchanged. And key buffer usage alway
I concur.
The SELECT time is going to resemble something like:
K_1 * F_1(number_of_records_in_database) + K_2 *
F_2(number_of_records_selected)
If the indices are effective, F_1 = log(N), but if the indices are not
effective, F_1 = N.
One thing you may want to try to narrow down the problem is
On Thu, Sep 4, 2008 at 10:38 AM, mos <[EMAIL PROTECTED]> wrote
Jim,
The problem is likely your index is not defined properly. Use an "Explain"
in front of the query to see if it can use just one index from each table.
I would try building a compound index on
Products: (RecordReference, FeedId)
On Wed, Sep 3, 2008 at 1:05 PM, Jim Leavitt <[EMAIL PROTECTED]> wrote:
>
> We are having trouble with certain queries which are returning anywhere
> from 10 - 30 rows. Total query time is taking approx 1 - 2 mins
> depending on load. Is there anything in our conf file which could improve
10 matches
Mail list logo
