All,
We're getting closer to the v3.0 feature freeze which is going to happen
this summer. Everything roadmapped for v3 but not implemented before the
deadline will be postponed. The next-after-v3 release is likely to
incorporate most of the postponed features, but there may be new
features
Add timing statistics to the monitoring tables
--
Key: CORE-4402
URL: http://tracker.firebirdsql.org/browse/CORE-4402
Project: Firebird Core
Issue Type: Improvement
Components: Engine
Allow referencing cursors as record variables in PSQL
-
Key: CORE-4403
URL: http://tracker.firebirdsql.org/browse/CORE-4403
Project: Firebird Core
Issue Type: Improvement
-Original Message-
From: Dmitry Yemanov (JIRA) [mailto:trac...@firebirdsql.org]
Sent: Jueves, 24 de Abril de 2014 10:55
Either explicit (DECLARE AS CURSOR) or implicit (FOR SELECT)
PSQL cursors could make their current record available via
the cursor name similar to OLD/NEW
24.04.2014 18:56, Claudio Valderrama C. wrote:
What I see is that fields with the same name, even though they come from
different tables, would need to be given an alias:
select T1.A, T2.A ... as cursor C do
v = C.A; -- Error
=
select T1.A as t1a, T2.A as t2a ... as cursor C do
On 24/04/2014 12:58, Dimitry Sibiryakov wrote:
24.04.2014 18:56, Claudio Valderrama C. wrote:
What I see is that fields with the same name, even though they come from
different tables, would need to be given an alias:
select T1.A, T2.A ... as cursor C do
v = C.A; -- Error
=
select
Claudio,
Is this feature being asked for?
;-)
Yes and it's very handy for people with an Oracle background. I wished
it was here in Firebird when I was its user back in 2000 ;-)
What I see is that fields with the same name, even though they come from
different tables, would need to be
