Just to be sure: is it true, that I don't need to change my stored
procedures concerning this breaking change

<<
You must now use string expressions for column references in the SQL/PSM
cursor FETCH, INSERT, and UPDATE statements.
>>

as long as I don't change these routines?

How about changing other routines which are not concerned? Does this
require the concerned routines to be updated to v. 2.04?

Thanks Uli

Uli,

This must be confirmed by Tim, but my understanding is that the issue is, if for any reason the routines have to be recompiled by EDB, they will fail, but as long as that doesn't happen, they will continue working well.

However, I'd upgrade them all, that's what I'm doing.
Its some work, yes, but not thaaat hard, and I'm sleeping better after upgrading them
Its that king of thing that you will do once, and forget .

--
Fernando Dias
[Team Elevate]


Em 06-12-2010 12:19, Uli Becker escreveu:
> Just to be sure: is it true, that I don't need to change my stored procedures concerning this breaking change
>
> <<
> You must now use string expressions for column references in the SQL/PSM cursor FETCH, INSERT, and UPDATE statements.
>  >>
>
> as long as I don't change these routines?
>
> How about changing other routines which are not concerned? Does this require the concerned routines to be updated to v. 2.04?
>
>

Thanks Uli

Fernando,

> However, I'd upgrade them all, that's what I'm doing.
> Its some work, yes, but not thaaat hard, and I'm sleeping better after
> upgrading them
> Its that king of thing that you will do once, and forget .

You are right for sure.

But it's not that easy for me to upgrade all databases on all my
customer's machines. That's why I asked.

I'll think about it though.

Thanks Uli

Uli,

You could perhaps add a script to your application to do the changes, and
run it automatically when your application starts or if its not possible,
pack it in an exe and send it to your customers for them to apply the
changes.

--
Fernando Dias
[Team Elevate]

Fernando,

> You could perhaps add a script to your application to do the changes,
> and run it automatically when your application starts or if its not
> possible, pack it in an exe and send it to your customers for them to
> apply the changes.

I know. But since there are several applications running in C/S mode
and there are always tables in use, I have to upgrade all databases and
all applications at the same time. That's the problem.

Uli

Uli,

Heh, then you have a difficult case, but its not different from when you need to alter the structure of a table or do any other database change.

--
Fernando Dias
[Team Elevate]

Fernando,

> Heh, then you have a difficult case, but its not different from when you
> need to alter the structure of a table or do any other database change.

Right!

Uli

Uli,

<< as long as I don't change these routines? >>

Correct.  EDB tracks the "creation version" of the routine (procedure,
function, trigger) and will not parse it using the new 2.04 syntax until you
actually alter the routine using 2.04.

<< How about changing other routines which are not concerned? Does this
require the concerned routines to be updated to v. 2.04? >>

No.  Each routine has its version initially set to the same version as the
catalog, and then that version is saved when the catalog is modified.  So if
you modify routine A using 2.04, then the catalog will be updated to 2.04
along with routine A, but routines B and C will still have their routine
version set to 2.03 (or whatever version the catalog was prior to the mods)
until you actually modify them.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> No.  Each routine has its version initially set to the same version as
> the catalog...

Thanks for the clarification.

Uli