Re: [Firebird-devel] Crash when caught exception is stored in StaticStatusVector

2016-04-11 Thread Dmitry Yemanov
11.04.2016 22:49, Dimitry Sibiryakov wrote: > Let me show that on example from TempSpace::setupFile(): > >> Firebird::StaticStatusVector status_vector; > . >> try >> { > . >> catch (const Firebird::system_error& ex) >> { >>

[Firebird-devel] Crash when caught exception is stored in StaticStatusVector

2016-04-11 Thread Dimitry Sibiryakov
Let me show that on example from TempSpace::setupFile(): > Firebird::StaticStatusVector status_vector; . > try > { . > catch (const Firebird::system_error& ex) > { > ex.stuffException(status_vector);

[Firebird-devel] [FB-Tracker] Created: (CORE-5194) Invalid computed by definition generated by isql -x

2016-04-11 Thread Carlos H. Cantu (JIRA)
Invalid computed by definition generated by isql -x --- Key: CORE-5194 URL: http://tracker.firebirdsql.org/browse/CORE-5194 Project: Firebird Core Issue Type: Bug Components: ISQL

Re: [Firebird-devel] Feature request & discussion for V4 (same as for V3)

2016-04-11 Thread Ann Harrison
On Mon, Apr 11, 2016 at 7:40 AM, Dimitry Sibiryakov wrote: > 11.04.2016 13:28, Dmitry Yemanov wrote: > > But it can be made possible. The question is whether it's worth it. > >While bug with orphan index nodes is living in the engine - index only > scan is > impossible completely. > Without

Re: [Firebird-devel] Feature request & discussion for V4 (same as for V3)

2016-04-11 Thread Atri Sharma
> > > > > > > This optimization can only be done if constant conditions are in the > > SQL, so +0 like tricks would not be affected. > > I already considered that, it seems easy enough to implement. > > > > Worth having? -- Regards, Atri *l'apprenant* -

Re: [Firebird-devel] Feature request & discussion for V4 (same as for V3)

2016-04-11 Thread Atri Sharma
On Mon, Apr 11, 2016 at 6:15 PM, Dmitry Yemanov wrote: > 11.04.2016 14:40, Dimitry Sibiryakov wrote: > > > > While bug with orphan index nodes is living in the engine - index only > scan is > > impossible completely. > > Pure index-only scan - maybe. It's impossible without transaction > numbers

Re: [Firebird-devel] Feature request & discussion for V4 (same as for V3)

2016-04-11 Thread Dmitry Yemanov
11.04.2016 14:40, Dimitry Sibiryakov wrote: > > While bug with orphan index nodes is living in the engine - index only scan is > impossible completely. Pure index-only scan - maybe. It's impossible without transaction numbers in indices too. But there may be other alternatives to consider. > Tra

[Firebird-devel] [FB-Tracker] Created: (CORE-5193) Operator precedence problem when use: NOT - in complex boolean expression

2016-04-11 Thread Pavel Zotov (JIRA)
Operator precedence problem when use: NOT - in complex boolean expression Key: CORE-5193 URL: http://tracker.firebirdsql.org/browse/CORE-5193 Project: Fire

Re: [Firebird-devel] Feature request & discussion for V4 (same as for V3)

2016-04-11 Thread Dimitry Sibiryakov
11.04.2016 13:28, Dmitry Yemanov wrote: > But it can be made possible. The question is whether it's worth it. While bug with orphan index nodes is living in the engine - index only scan is impossible completely. Transformation numeric->double can loose data. Using integers as a key will d

Re: [Firebird-devel] Feature request & discussion for V4 (same as for V3)

2016-04-11 Thread Dmitry Yemanov
11.04.2016 14:16, Dimitry Sibiryakov wrote: > 11.04.2016 13:08, Molnár Attila wrote: >> It's hard and costly (or even possible) to deconstruct the index format to >> get the >> original column values? > > Yes, in common case it is impossible. But it can be made possible. The question is whether

Re: [Firebird-devel] Feature request & discussion for V4 (same as for V3)

2016-04-11 Thread Dmitry Yemanov
11.04.2016 14:08, Molnár Attila wrote: > >> When InterBase was created, there was a lot of academic work on >> optimizing corner cases, with the result that academic databases >> tended to spend more time optimizing than retrieving. We made the >> deliberate choice not to spend optimizer time savi

Re: [Firebird-devel] Feature request & discussion for V4 (same as for V3)

2016-04-11 Thread Dimitry Sibiryakov
11.04.2016 13:08, Molnár Attila wrote: > It's hard and costly (or even possible) to deconstruct the index format to > get the > original column values? Yes, in common case it is impossible. -- WBR, SD. -- Find an

Re: [Firebird-devel] Feature request & discussion for V4 (same as for V3)

2016-04-11 Thread Molnár Attila
On 2016.04.09. 20:25, Ann Harrison wrote: On Fri, Apr 8, 2016 at 5:54 AM, Molnár Attila wrote: Optimizations