* According to Fedora packaging rules, firebird service is not started
automatically. You need to start it, as root :
systemctl start firebird-superclassic.service
for Classic :
systemctl start firebird-classic.socket
If you want to have firebird started at each boot, as root :
systemctl enable
At 11:25 p.m. 23/01/2015, michael.vilhelm...@microcom.dk [firebird-support]
wrote:
I am looking for a function which are able to add values from a table as
records are fetched.
Something like this:
ValueCalculated value
11
23
36
410
515
The calculated value is just the sum of all
Select trim(RC.RDB$INDEX_NAME)
from RDB$RELATION_CONSTRAINTS RC
where (RC.RDB$CONSTRAINT_TYPE = 'PRIMARY KEY') and
(RC.RDB$RELATION_NAME = :TABELA)
into :PKTEMP
Using that select you can fiind the name of the column who has the primary
key.
Inspired from Carlos Cantu external log
Hello,
I have an application that use a Firebird database and I need to
change a Primary Key on a table by adding a new field.
I can drop a primary key constraint by ALTER TABLE MyTable DROP
CONSTRAINT MyINTEG_000 where MyINTEG_000 is the constraint on my
development database file.
I
Select trim(I.RDB$FIELD_NAME)
from RDB$RELATION_CONSTRAINTS RC
join RDB$INDEX_SEGMENTS I on (I.RDB$INDEX_NAME = RC.RDB$INDEX_NAME)
join RDB$INDICES IDX on (IDX.RDB$INDEX_NAME = RC.RDB$INDEX_NAME)
where (RC.RDB$CONSTRAINT_TYPE = 'PRIMARY KEY') and
On Mon, 26 Jan 2015 19:05:33 +0100, Luigi Siciliano
luigi...@tiscalinet.it
[firebird-support] firebird-support@yahoogroups.com wrote:
Hello,
I have an application that use a Firebird database and I need to
change a Primary Key on a table by adding a new field.
I can drop a primary key
Hi Dimitry,
thank you for your response.
I think in my case I can replace the outer join with an inner join, because it
is the same sp with the same query parameters I am calling twice.
Are there any future plans to change this re-evaluation structure in outter
joins?
Kind regards
Christian
On 26/01/2015 09:53, masb...@za-management.com [firebird-support] wrote:
Hi Dimitry,
thank you for your response.
I think in my case I can replace the outer join with an inner join,
because it is the same sp with the same query parameters I am calling
twice.
Are there any future plans to
