I'm trying to get my head round this issue. I like the look of what I think I'll be able to achieve with the extra capabilities.

The way I'm rewriting my app means that there may be many instances of the database (damned if I know the right words so I hope you understand) with identical structure but different data. With ElevateDB this means that the functions etc will be replicated in each instance.

What I was thinking of doing was having a template database in the same directory as the app and initially all changes to structure, functions etc get made into there THEN if one of the instances is checked the first thing the app does is check versions of everything and if necessary update.

I like the concept, but I'm not sure how to do it - there are no version numbers for functions, procedures, triggers etc.

Any comments on my idea and more importantly any idea on implementing it?


Roy Lambert

Roy,

<< The way I'm rewriting my app means that there may be many instances of
the database (damned if I know the right words so I hope you understand)
with identical structure but different data. With ElevateDB this means that
the functions etc will be replicated in each instance.

What I was thinking of doing was having a template database in the same
directory as the app and initially all changes to structure, functions etc
get made into there THEN if one of the instances is checked the first thing
the app does is check versions of everything and if necessary update.

I like the concept, but I'm not sure how to do it - there are no version
numbers for functions, procedures, triggers etc.

Any comments on my idea and more importantly any idea on implementing it?
>>

What you really need are SQL code modules, and EDB doesn't have them yet.
They are basically libraries of functions and procedures that can be defined
in one place and called from any database.

For now, however, your best bet is something along the lines of what you
outline above.  You'll have to simply rely on a string comparison of the
function body via the catalog functions to determine whether the function is
different or not.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>What you really need are SQL code modules, and EDB doesn't have them yet.
>They are basically libraries of functions and procedures that can be defined
>in one place and called from any database.

They sound nice - I like the "yet" it implies we will get them - how's about as a late Xmas present for this year or a VERY early one for next

Roy Lambert

ps This just proves that you're right - never tell us about forward plans cos we'll want it NOW!!!!!