At 07:31 a.m. 8/08/2015, 'stwizard' stwiz...@att.net [firebird-support] wrote:
Correction:
I met to say I then installed FreeAdhocUDF not FreeUDFLib library.
You said:
I verified that the function is defined with the following:
select * from rdb$functions where upper(rdb$function_name) =
On Aug 7, 2015, at 1:56 PM, 'Walter R. Ojeda Valiente'
sistemas2000profesio...@gmail.com [firebird-support]
firebird-support@yahoogroups.com wrote:
Well, after run GSTAT and reading the output I can see how many garbage a
whole table has, but it don't shows me the story of a row. ¿How
On 07/08/15 06:30, liviuslivius liviusliv...@poczta.onet.pl
[firebird-support] wrote:
Why do you need to go back?
There is still a lot of code in use that will not run with 2.5 and
running both versions can be a bit of a nightmare. I've restored on the
wrong machine myself while looking to do
Well, after run GSTAT and reading the output I can see how many garbage a
whole table has, but it don't shows me the story of a row. ¿How many
COMMITs and how many ROLLBACKs the row with ID 1234 of the table CLIENTS
had had?
Greetings.
Walter.
On Fri, Aug 7, 2015 at 1:42 PM, Walter R. Ojeda
Greetings All,
On a new Windows 7 64 bit computer I installed Firebird v2.5.4 64 bit
I then installed the FreeUDFLib 64bit functions
I then did a firebird v1.5.3 backup of the metadata only and then restored this
on firebird v2.5.4.
I made sure to use the following switches during the
The idea is to know how many garbage a table has. Or several tables. Or the
whole database.
That you can find out with gstat. It won't tell you how bad each record is,
but it will tell you the total number of back version, average, min, and max
chain lenght.
Then you can set up
Thank you Ann, I shall investigate that.
Greetings.
Walter.
On Fri, Aug 7, 2015 at 1:10 PM, Ann Harrison aharri...@ibphoenix.com
[firebird-support] firebird-support@yahoogroups.com wrote:
The idea is to know how many garbage a table has. Or several tables. Or
the whole database.
Correction:
I met to say I then installed FreeAdhocUDF not FreeUDFLib library.
And according to their website I also install the 4 icu*44FAU.dll files to the
Bin folder.
http://freeadhocudf.org/documentation_english/dok_eng_icu.html
I’ve rebooted the computer too, so I’m at a loss
Yes, of course that I can use triggers but that will have 2 problems:
1. Just will work with *new* data, not with the old ones. The data commited
or rolled back *before* I write the triggers will be ignored.
2. With a database trigger I can know if a transaction has ends with a
COMMIT or a ROLL
Hello everybody
Do you know why this simple trigger hang-up the database?
CREATE TRIGGER TRANSACCION_INICIA
ACTIVE ON TRANSACTION START
POSITION 0
AS
BEGIN
IN AUTONOMOUS TRANSACTION DO BEGIN
END
END;
Always when I put IN AUTONOMOUS TRANSACTION the database crash. Without
those words
At 02:51 p.m. 8/08/2015, 'Walter R. Ojeda Valiente'
sistemas2000profesio...@gmail.com [f wrote:
Hello everybody
Do you know why this simple trigger hang-up the database?
CREATE TRIGGER TRANSACCION_INICIA
ACTIVE ON TRANSACTION START
POSITION 0
AS
BEGIN
 Â
  IN AUTONOMOUS TRANSACTION DO
Ha, ha, ha, ha, ha, ha, ha, ha.
Thank you very much Helen, sometimes the memory is not so good as was some
years ago.
Ok, I now know and hope not forget again: NEVER USE IN AUTONOMOUS
TRANSACTION INSIDE A TRANSACTION RELATED DATABASE TRIGGER.
Greetings.
Walter.
On Fri, Aug 7, 2015 at 11:20
12 matches
Mail list logo