2007 13H31 (GMT-0400) America/Santiago
Asunto: Re: Problem with compex query
Hi Patricio,
Your explain is scary.No use of index...Please, ask to programers in
order to create some index in the schema.
Development Server has the same version of MySQL production environment?.
4.0.18 ?
PROTECTED]>
Cc: mysql@lists.mysql.com
Enviados: martes 22 de mayo de 2007 13H31 (GMT-0400) America/Santiago
Asunto: Re: Problem with compex query
Hi Patricio,
Your explain is scary.No use of index...Please, ask to programers in order
to create some index in the schema.
Develo
Hi Patricio,
Your explain is scary.No use of index...Please, ask to programers in
order to create some index in the schema.
Development Server has the same version of MySQL production environment?.
4.0.18?
Resume:
1) Please check the version of mysql ( prod and development)
2) Please use i
Juan Eduardo,
Great to hear about you :)
One thing you must know is that i can run this query from a mysql client,
without the insert part.
The problem only happens when is run from the J2EE (Websphere - drp)
application.
I run the query as you asked, here are some results:
++-
Hi Patricio,
Some options are to prevent programmers/users make a "bad" queries into
the database' SQL_BIG_SELECTS = 0 | 1
The documentation say :
"If set to 0, MySQL will abort if a SELECT is attempted that probably will
take a very long time. This is useful when an inadvisable WHERE statemen
Friends,
im having troubles with the following query:
---
INSERT drp_volumen_venta_diaria_deposito (drp_id_sku, drp_id_deposito,
drp_volumen, drp_es_cct, drp_dia, drp_mes, drp_anno, drp_fecha_dia_cargado )
SELECT DISTINCT s.drp_id_sku, d.drp
