On 1/28/10 5:21 AM, "changuno" wrote:
> Hi folks,
>
> Read a blog which states 50 things to know before migrating from Oracle to
> MySQL. Any comments on this?
as a relatively unsophisticated dbms user (just dynamic web site back end),
i thought it was very interesting to see the kinds of thing
On 1/21/10 12:03 PM, "Price, Randall" wrote:
> I have a two databases, one in a production environment (let's call it
> db_prod) and the other in a testing environments (Let's call it db_test).
>
> What is the best way to synchronize the database schemas? db_test has had a
> few indexes and con
non-linearity in the insert rate means you have indexes on some columns.
depending on your situation, mysql can be more efficient if drop those
indexes, do bulk inserts, and then add the indexes again.
On 1/23/10 5:02 AM, "Krishna Chandra Prajapati"
wrote:
> Hi shawn,
>
> As the data grows to
On 1/21/10 10:27 AM, "John Campbell" wrote:
> I want to find rows that contain a word that matches a term, accent
> insensitive: I am using utf8-general collation everywhere.
>
> attempt 1:
> SELECT * FROM t WHERE txt LIKE '%que%'
> Matches que qué, but also matches 'queue'
>
> attempt 1.5:
>
that's exactly how i do it.
On 1/19/10 3:57 PM, "Intell! Soft" wrote:
> Thanks! - I found a Insert Into on your tip:
>
> Insert Into Lieferanten (Lieferant)
> select distinct
> a.lieferant
> from artikelstamm a
> left join lieferanten b on
> a.lieferant = b.lieferant
> where
> b.lief
On 1/19/10 2:19 AM, "Ningappa Koneri" wrote:
> 3.It worked even after removing tag from the head tag as well <-- plz
> through some light y it got displayed at the browser ?
this is not a mysql question. but see:
http://www.w3.org/TR/1999/REC-html401-19991224/charset.html#h-5.2.2
the likelih
you can specify the character encoding (called CHARSET in mysql) and
collation on a per column, per table or per database level. e.g.
CREATE DATABASE foo CHARACTER SET utf8 COLLATE utf8_general_ci;
or
CREATE TABLE foo ( ... ) CHARACTER SET utf8 COLLATE utf8_general_ci;
or
CREATE TABLE foo (
ba
the example you gave would work with a range constraint:
WHERE `bar_id` > 0 AND `bar_id` < 63
but i guess this is not a general solution.
i've done exactly this kind of select using an IN constraint very often.
i've not had any trouble with lists of a few hundred so long as i have the
necessar
On 1/15/10 12:01 AM, "Junior Ortis" wrote:
> Hi guys i have a problem, 3 big tables: item_instance about 15KK rows,
> character_inventory 15KK rows, guild_bank_item 2KK rows.
>
> And i need i clean on item_instance how this query:
>
> DELETE FROM `item_instance` WHERE guid NOT IN(SELECT item FR
On 1/13/10 2:28 PM, "Lawrence Sorrillo" wrote:
> The issue is that in theory this should work given the facts announced
> by MySQL regarding binary logging and replication.
> I can certainly do it the way you propose, but to my mind I should also
> be able to do it using the fact that both machin
10 matches
Mail list logo
