[Firebird-devel] ADO.NET provider 5.10.0.0

2017-08-24 Thread Jiří Činčura
More info:
https://www.tabsoverspaces.com/233641-ado-net-provider-5-10-0-0-for-firebird-is-ready/
.

-- 
Mgr. Jiří Činčura
Independent IT Specialist

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


Re: [Firebird-devel] Firebird 4.0 Alpha 1 release is available for testing

2017-08-24 Thread Dmitry Yemanov

24.08.2017 23:34, livius wrote:


However i see that context limit is "the same" for the single query
Is this really plan for Firebird4 or it is postponed?


It will be removed in the next Alpha/Beta release.


Dmitry

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


Re: [Firebird-devel] Firebird 4.0 Alpha 1 release is available for testing

2017-08-24 Thread livius

Hi,

first i must thank you for great work :)

I really wait for frame in window funcion, longer indentifiers and bigger 
database page size. And i test this intensively.


However i see that context limit is "the same" for the single query
Is this really plan for Firebird4 or it is postponed?
http://tracker.firebirdsql.org/browse/CORE-809
And if it is plan for it, it will be increassed/removed for single query 
also or only form procedures/triggers?


regards,
Karol Bieniaszewski


-Oryginalna wiadomość- 
From: Dmitry Yemanov

Sent: Thursday, August 24, 2017 10:11 AM
To: For discussion among Firebird Developers
Subject: [Firebird-devel] Firebird 4.0 Alpha 1 release is available for 
testing


Firebird Project announces the first Alpha release of Firebird 4.0, the
next major version of the Firebird relational database, which is now
available for testing.

This Alpha release arrives with an early preview of the features and
improvements currently under development by the Firebird development
team, as well as with countless bugfixes. Our users are appreciated
giving it a try and providing feedback to this mailing list. Apparent
bugs can be reported directly to the bugtracker.

Alpha releases are not encouraged for production usage or any other
goals that require a stable system. They are, however, recommended for
those users who want to help in identifying issues and bottlenecks thus
allowing to progress faster through the Beta/RC stages towards the final
release.

Please read the Release Notes carefully before installing and testing
this Alpha release.


Download page:
http://www.firebirdsql.org/en/firebird-4-0-0-alpha1/

Release Notes:
http://web.firebirdsql.org/downloads/prerelease/v40alpha1/Firebird-4.0.0_Alpha1-ReleaseNotes.pdf


--
Dmitry Yemanov

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel 



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


Re: [Firebird-devel] block size exceeds implementation restriction at JStatement::openCursor

2017-08-24 Thread Leyne, Sean

>> Here's the plan:
>> PLAN HASH (EMTD NATURAL, JOIN (SORT (DR DR NATURAL), EWR INDEX
>> (IDX_EWR_SENT_A_TEMP)))

> Post a tracker entry to have it fixed. Or create an index for joining.

This suggests that the issue is JOINing based on a NATURAL scan of the related 
table.  Correct?

{Trying to determine how the tracker case should best be described -- the 
current " block size exceeds implementation restriction at 
JStatement::openCursor" is the error, the case subject should describe the 
cause}


Sean

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


[Firebird-devel] [FB-Tracker] Created: (CORE-5598) block size exceeds implementation restriction at JStatement::openCursor

2017-08-24 Thread Jiri Cincura (JIRA)
block size exceeds implementation restriction at JStatement::openCursor
---

 Key: CORE-5598
 URL: http://tracker.firebirdsql.org/browse/CORE-5598
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 3.0.2
Reporter: Jiri Cincura


I have a query that on one particular database throws:

2017-08-24T16:29:11.5140 (2704:01620040) ERROR AT
JStatement::openCursor
I:\DOWNLOADS\BI2.FDB (ATT_16, SYSDBA:NONE, NONE,
TCPv6:::1/51084)

C:\Users\Jiri\Documents\devel\bin\Firebird-3.0.2.32703-0_x64\isql.exe:7116
335544381 : Implementation limit exceeded
335544388 : block size exceeds implementation restriction

On other databases (same structure, same plan produced) on the same
server (different data of course) it works fine. Backup & restore didn't
help. I can provide the database, but given it's a customer data it
needs to be handled as private data. 

The minimum query I can replicate it looks like this:
with DAYS 
as (select distinct(DR.F_DA_DATE) 
from T_DAILY_RAW DR 
) 
select count(*) 
from T_EMAILS_WEBDB_RAW EWR 
inner join DAYS DR on DR.F_DA_DATE = EWR.F_EWR_SENT 
inner join T_EMAIL_TYPE_DIM EMTD on EMTD.F_EMT_VALUE = EWR.F_EWR_TYPE;

And the plan is "PLAN HASH (EMTD NATURAL, JOIN (SORT (DR DR NATURAL), EWR 
INDEX(IDX_EWR_SENT_A_TEMP)))". 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


Re: [Firebird-devel] block size exceeds implementation restriction at JStatement::openCursor

2017-08-24 Thread Jiří Činčura
> Post a tracker entry to have it fixed. Or create an index for joining.

Done http://tracker.firebirdsql.org/browse/CORE-5598.

-- 
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


Re: [Firebird-devel] block size exceeds implementation restriction at JStatement::openCursor

2017-08-24 Thread Dmitry Yemanov
Post a tracker entry to have it fixed. Or create an index for joining.Dmitry18:35, 24 августа 2017 г., "Jiří Činčura" : What is the plan? I suspect some hardcoded limit for the hash join  algorithm has been reached. Do you see HASH in the plan?Here's the plan:PLAN HASH (EMTD NATURAL, JOIN (SORT (DR DR NATURAL), EWR INDEX(IDX_EWR_SENT_A_TEMP)))Could I somehow confirm it's this? And more importantly how can Iprevent falling into this trap? :)-- Mgr. Jiří Činčurahttps://www.tabsoverspaces.com/--Check out the vibrant tech community on one of the world's mostengaging tech sites, Slashdot.org! http://sdm.link/slashdotFirebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel-- Отправлено из мобильного приложения Яндекс.Почты--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdotFirebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


Re: [Firebird-devel] block size exceeds implementation restriction at JStatement::openCursor

2017-08-24 Thread Jiří Činčura
> What is the plan? I suspect some hardcoded limit for the hash join 
> algorithm has been reached. Do you see HASH in the plan?

Here's the plan:
PLAN HASH (EMTD NATURAL, JOIN (SORT (DR DR NATURAL), EWR INDEX
(IDX_EWR_SENT_A_TEMP)))

Could I somehow confirm it's this? And more importantly how can I
prevent falling into this trap? :)

-- 
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


Re: [Firebird-devel] block size exceeds implementation restriction at JStatement::openCursor

2017-08-24 Thread Dmitry Yemanov

24.08.2017 17:50, Jiří Činčura wrote:


I have a query that on one particular database throws:

2017-08-24T16:29:11.5140 (2704:01620040) ERROR AT
JStatement::openCursor
 I:\DOWNLOADS\BI2.FDB (ATT_16, SYSDBA:NONE, NONE,
 TCPv6:::1/51084)
 
C:\Users\Jiri\Documents\devel\bin\Firebird-3.0.2.32703-0_x64\isql.exe:7116
335544381 : Implementation limit exceeded
335544388 : block size exceeds implementation restriction

On other databases (same structure, same plan produced) on the same
server (different data of course) it works fine. Backup & restore didn't
help. I can provide the database, but given it's a customer data it
needs to be handled as private data.

The minimum query I can replicate it looks like this:
with DAYS
as (select distinct(DR.F_DA_DATE)
 from T_DAILY_RAW DR
)
select count(*)
from T_EMAILS_WEBDB_RAW EWR
inner join DAYS DR on DR.F_DA_DATE = EWR.F_EWR_SENT
inner join T_EMAIL_TYPE_DIM EMTD on EMTD.F_EMT_VALUE = EWR.F_EWR_TYPE;


What is the plan? I suspect some hardcoded limit for the hash join 
algorithm has been reached. Do you see HASH in the plan?



Dmitry

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


Re: [Firebird-devel] block size exceeds implementation restriction at JStatement::openCursor

2017-08-24 Thread Jiří Činčura
Hmm, if I change the last join to use "on cast(EMTD.F_EMT_VALUE as
varchar(377) character set utf8) = cast(EWR.F_EWR_TYPE as varchar(377)
character set utf8)" it works (378 fails again). 377 doesn't ring a bell
for me to run over some limit.

Wondering how is it working on other databases.

-- 
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


[Firebird-devel] block size exceeds implementation restriction at JStatement::openCursor

2017-08-24 Thread Jiří Činčura
Hi,

I have a query that on one particular database throws:

2017-08-24T16:29:11.5140 (2704:01620040) ERROR AT
JStatement::openCursor
I:\DOWNLOADS\BI2.FDB (ATT_16, SYSDBA:NONE, NONE,
TCPv6:::1/51084)

C:\Users\Jiri\Documents\devel\bin\Firebird-3.0.2.32703-0_x64\isql.exe:7116
335544381 : Implementation limit exceeded
335544388 : block size exceeds implementation restriction

On other databases (same structure, same plan produced) on the same
server (different data of course) it works fine. Backup & restore didn't
help. I can provide the database, but given it's a customer data it
needs to be handled as private data. 

The minimum query I can replicate it looks like this:
with DAYS 
as (select distinct(DR.F_DA_DATE) 
from T_DAILY_RAW DR 
) 
select count(*) 
from T_EMAILS_WEBDB_RAW EWR 
inner join DAYS DR on DR.F_DA_DATE = EWR.F_EWR_SENT 
inner join T_EMAIL_TYPE_DIM EMTD on EMTD.F_EMT_VALUE = EWR.F_EWR_TYPE;

Removing the distinct (I know, it's useless for the end result in this
case) makes the query finish fine.

Can I pinpoint why is this happening?

-- 
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


[Firebird-devel] [FB-Tracker] Created: (CORE-5597) Failing isc_que_events causes that other operations with DB on same handle are blocked

2017-08-24 Thread Slavomir Skopalik (JIRA)
Failing isc_que_events causes that other operations with DB on same handle are 
blocked
--

 Key: CORE-5597
 URL: http://tracker.firebirdsql.org/browse/CORE-5597
 Project: Firebird Core
  Issue Type: Bug
  Components: API / Client Library
Affects Versions: 2.5.7
 Environment: Windows, DelphiXE7, simplified (no thread) implementation 
of IBEvent
Reporter: Slavomir Skopalik
Priority: Minor


32 bits gds32.dll from 2.5.7
In case that connection to DB was successfully but auxiliary event connection 
failed to establish, other operations on same DB handle are  blocked.

Call of isc_cancel_events not help.

If I use fbclient.dll from Firebird-3.0.3.32798-0_Win32, it is working fine.




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


Re: [Firebird-devel] Firebird 4.0 Alpha 1 release is available for testing

2017-08-24 Thread Gabor Boros

Hi All,

Thank you for all who worked on it, tested it, documented it, etc.! :-)

Gabor

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel


[Firebird-devel] Firebird 4.0 Alpha 1 release is available for testing

2017-08-24 Thread Dmitry Yemanov

Firebird Project announces the first Alpha release of Firebird 4.0, the
next major version of the Firebird relational database, which is now
available for testing.

This Alpha release arrives with an early preview of the features and
improvements currently under development by the Firebird development
team, as well as with countless bugfixes. Our users are appreciated
giving it a try and providing feedback to this mailing list. Apparent
bugs can be reported directly to the bugtracker.

Alpha releases are not encouraged for production usage or any other
goals that require a stable system. They are, however, recommended for
those users who want to help in identifying issues and bottlenecks thus
allowing to progress faster through the Beta/RC stages towards the final
release.

Please read the Release Notes carefully before installing and testing
this Alpha release.


Download page:
http://www.firebirdsql.org/en/firebird-4-0-0-alpha1/

Release Notes:
http://web.firebirdsql.org/downloads/prerelease/v40alpha1/Firebird-4.0.0_Alpha1-ReleaseNotes.pdf


--
Dmitry Yemanov

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel