On 08/10/12 21:13, Dimitry Sibiryakov wrote:
> 10.08.2012 19:10, Adriano dos Santos Fernandes wrote:
>> Then bug will remains in embedded engine usage. It's not a good option
>> to let applications (ISQL or user ones) to deal with things that must
>> works automatically.
>Using locale informat
On 13/08/2012 04:29, Alex Peshkoff wrote:
> On 08/10/12 21:13, Dimitry Sibiryakov wrote:
>> 10.08.2012 19:10, Adriano dos Santos Fernandes wrote:
>>> Then bug will remains in embedded engine usage. It's not a good option
>>> to let applications (ISQL or user ones) to deal with things that must
>>>
On 08/13/12 14:37, Adriano dos Santos Fernandes wrote:
> On 13/08/2012 04:29, Alex Peshkoff wrote:
>> On 08/10/12 21:13, Dimitry Sibiryakov wrote:
>>> 10.08.2012 19:10, Adriano dos Santos Fernandes wrote:
Then bug will remains in embedded engine usage. It's not a good option
to let appl
Hello,
it's normal that only the indexes on one table is used during an inner
join ?
for exemple :
table a
ID => pk_index
DATE => index a_date => selectivity : 0.1
NAME => index a_name selectivity :0.1
table b :
REFIDA => fk_index
REFPRODUIT => index b_produit => selectivity : 0.2
NAME => in
On 13/08/2012 08:28, Alex Peshkoff wrote:
>> This seems completely wrong solution. Our caller may not even have easy
>> access to setlocale (of the same CRT as ours).
>>
> Taking into an account that posix build is used not only on linux (have
> you ever seen linux with >1 CRT?) I can agree with th
13.08.2012 19:15, arnaud le roy wrote:
>
> it's normal that only the indexes on one table is used during an inner
> join ?
>
> for exemple :
>
> table a
>
> ID => pk_index
> DATE => index a_date => selectivity : 0.1
> NAME => index a_name selectivity :0.1
>
> table b :
>
> REFIDA => fk_index
> REFP
On Mon, Aug 13, 2012 at 11:15 AM, arnaud le roy wrote:
>
> it's normal that only the indexes on one table is used during an inner
> join ?
>
No, but this is a support question, not a developer question, and should be
sent to firebird-supp...@yahoogroups.com. When you send your question
there, p
this is the detail :
CREATE TABLE A (
IDINTEGER NOT NULL,
DATEDOC TIMESTAMP NOT NULL,
WHEREDOC VARCHAR(22) NOT NULL
);
ALTER TABLE A ADD CONSTRAINT PK_A PRIMARY KEY (ID);
CREATE INDEX A_IDX1 ON A (DATEDOC);
CREATE INDEX A_IDX2 ON A (WHEREDOC);
CREATE TABLE B (
oh sorry but i post here because i have a doubt that this behaviour it's
not normal but effectively it's not the good mailing list.
my test are done on 2.5 super server on windows 7 64. in this little
test there is 1 lines in each table but in my real database i have
one milliom lines and s
