Steve Naidamast wrote:
> However, could you clarify what you mean between a session or a transaction?
Session == connection
I guess you know what a transaction is.
You can define a GTT with a life that lasts as long as the transaction
in which it is instantiated, i.e.,
CREATE GLOBAL TEMPORARY
Thank you! Thankfully I made the dialect 1 to 3 conversion years ago.
I will check these out. It will be a bit before I can devote 100% on this.
> On Feb 13, 2019, at 1:03 PM, FSPAPA INCA Team i...@foodstuffs-si.co.nz
> [firebird-support] wrote:
>
>
> Hi Kevin – I’ve had good results
Hi Kevin – I’ve had good results using fbclone to migrate from InterBase 7.5.1
to Firebird 3 using this method. Migrating from 1.5 might not be too
dissimilar.
https://github.com/zedalaye/fbclone
I made a couple of changes to support dialect 1 (we’re going to switch to
dialect 3 and remove
Hi Helen...
Thank you for clearing this up for me.
However, could you clarify what you mean between a session or a transaction?
Steve Naidamast
Sr. Software Engineer
Steve Naidamast wrote:
> By using a global table in Firebird, could not multiple users cause
> a conflict if two such users were to issue the same query against the global
> table?
No. A GTT definition is persistent, of course, but persistent data
are not stored in it. A GTT instance is
By using a global table in Firebird, could not multiple users cause a conflict
if two such users were to issue the same query against the global table?
Coming from a SQL Server background, I am used to using local temporary
tables, which are isolated on a query by query basis...
Steve
Good points Mark.
Then maybe some switch to restore process should be added?
Now this is nightmare for the end user.
regards,
Karol Bieniaszewski
Hi.
There are 2 common ways
1. Create global temporary table
Do INSERT INTO T(DSTART, DEND) SELECT …
and then do simple join with this table
2. Use derived table e.g.
SELECT
DATENLOGGING.* …
FROM
(SELECT D.DSTART, D.DEND FROM TABLED) X
LEFT JOIN DATENLOGGING ON DATENLOGGING.DATUMZEIT>=X. DSTART
On 13-2-2019 18:29, Kevin Stanton kevin.stan...@rdb-solutions.com
[firebird-support] wrote:
> Thanks Mark. I realize it’s a huge migration. I will be exhaustively
> testing everything. I like the idea of creating an empty database and
> pumping the data over. Is there a tool for this?
Does anybody has a idea to optimization my follow query?
SELECT
ELEMENTE.BEZEICHNUNG,
DATENLOGGING.DATUMZEIT,
DATENLOGGING.WERT,
DATENLOGGINGTYPEN.MASSEINHEIT,
DATENLOGGINGTYPEN.DATA_TYPE,
DATENLOGGINGTYPEN.FAKTOR
FROM
DATENLOGGING
INNER JOIN ELEMENTE
ON
13.02.2019 18:29, Kevin Stanton kevin.stan...@rdb-solutions.com
[firebird-support] wrote:
> I like the idea of creating an empty database and pumping the data over. Is
> there a tool
> for this? (Actually just found one from Clever Components)
I'd recommend to look at FBCopy/FBExport tools.
The restore are not validating the Stored Procedures! After recreation in FB3
you have to validate/compile you SP!
Regards
Gregor
Sent from Yahoo Mail. Get the app https://yho.com/148vdq
On 13-2-2019 17:48, Karol Bieniaszewski liviusliv...@poczta.onet.pl
[firebird-support] wrote:
> >>Recompiling stored
> >>procedures, triggers, etc is always a good thing to do when upgrading.
> >>Mark
>
> Why it is not done automatically on restore if there is source present?
I shouldn't
Thanks Mark. I realize it’s a huge migration. I will be exhaustively testing
everything. I like the idea of creating an empty database and pumping the data
over. Is there a tool for this? (Actually just found one from Clever
Components)
I have looked at the migration docs for the 2.x
On 13-2-2019 16:58, Kevin Stanton kevin.stan...@rdb-solutions.com
[firebird-support] wrote:
> I’m starting to look into migrating from 1.56 to either 2.5 or directly to
> 3.0. I’ve bought the Migration Guide but haven’t read it yet.
>
> It concerns me that I would/will have to recompile all
>>Recompiling stored
>>procedures, triggers, etc is always a good thing to do when upgrading.
>>Mark
Why it is not done automatically on restore if there is source present?
Pozdrawiam,
Karol Bieniaszewski
13.02.2019 16:39, Mark Rotteveel m...@lawinegevaar.nl [firebird-support] wrote:
> My bet is on the addition of the savepoint.
Yes, this is the way partial cursor stability is implemented in 3.0:
insert-select
cannot see changes made inside of the same savepoint, so sub-query in second
query
I’m starting to look into migrating from 1.56 to either 2.5 or directly to 3.0.
I’ve bought the Migration Guide but haven’t read it yet.
It concerns me that I would/will have to recompile all SPs and triggers. Is
there an automated way to do this? I have 909 SPs and 785 triggers. This will
I can reproduce it (Firebird 2.5.8 to Firebird 3.0.4).
I suggest that you create a ticket in the tracker. The problem doesn't
sound familiar to me, and if it is a known problem, the core developers
will close appropriately to an existing duplicate.
Looking at the BLR (using set blob all in
On 13-2-2019 07:57, wang...@yahoo.com [firebird-support] wrote:
> firebird 1.5 linux built is for 32 bits, is it possible to install it in
> a 64 bit linux? Thanks.
Firebird 1.5 has been unsupported for almost 10 years now. It is really
time to start upgrading.
I think the only way is to try
When migrating from Firebird 2.5 to Firebird 3 we have a number of stored
procedures that stop functioning correctly. They start working again once
the procedures have been rebuilt from script.
The procedures all perform something along the lines of inserting a record
with a default value and then
> firebird 1.5 linux built is for 32 bits, is it possible to install it
> in a 64 bit linux? Thanks.
As long as your 64Bit Linux does have support for 32Bit and the required
32Bit runtimes are installed it should be possible to install.
22 matches
Mail list logo