Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Deploying NEW table structures -- Best Way
Sat, May 8 2010 12:12 PMPermanent Link

Dan

I am looking at purchasing DBISAM and am wondering what is the best way to apply new data structures to existing installed applications.  For example, if an existing table has a new field or has a change to an existing field, do I have to keep track of all the modifications and then apply them via SQL queries?

I am using a lot of BDE -> Paradox tables currently.  I have a utility that uses the dbi functionality in the bde unit.  IT allows me to export the table structures, indexes, and keys to a text file.  That text file can be parsed and the changes applied to the depolyed database in one command.  I am looking for something equivelant.

Thank you for any ideas.

DAN
Sat, May 8 2010 2:06 PMPermanent Link

Robert Kaplan


<Dan> wrote in message
news:EF8C169D-DF31-4615-99B3-28857D920277@news.elevatesoft.com...
>I am looking at purchasing DBISAM and am wondering what is the best way to
>apply new data structures to existing installed applications.  For example,
>if an existing table has a new field or has a change to an existing field,
>do I have to keep track of all the modifications and then apply them via
>SQL queries?
>
> I am using a lot of BDE -> Paradox tables currently.  I have a utility
> that uses the dbi functionality in the bde unit.  IT allows me to export
> the table structures, indexes, and keys to a text file.  That text file
> can be parsed and the changes applied to the depolyed database in one
> command.  I am looking for something equivelant.
>
> Thank you for any ideas.
>

I have a simple method that works fairly well for me. In one of the tables
(does not matther which, pick one), I use the user minor version to keep
track of the database  "version" (my version, not dbisam's). Then on the
datamodule I have a constant with the current version number. The new
releases include not only the new programs, but also SQL scripts that update
the tables - including changing the user minor version on my control table.

Then when the program starts, before I attempt to do any database activity
or even open any table, I compare the datamodule constant with the user
minor version on my control table and if they don't match then apply the
corresponding upgrades. To keep it simple, the upgrade files correspond to
the tables version (upgrade01.SQL upgrade02.SQL etc)

Robert

Sat, May 8 2010 6:22 PMPermanent Link

Dan

"Robert K" wrote:


<Dan> wrote in message
news:EF8C169D-DF31-4615-99B3-28857D920277@news.elevatesoft.com...
>I am looking at purchasing DBISAM and am wondering what is the best way to
>apply new data structures to existing installed applications.  For example,
>if an existing table has a new field or has a change to an existing field,
>do I have to keep track of all the modifications and then apply them via
>SQL queries?
>
> I am using a lot of BDE -> Paradox tables currently.  I have a utility
> that uses the dbi functionality in the bde unit.  IT allows me to export
> the table structures, indexes, and keys to a text file.  That text file
> can be parsed and the changes applied to the depolyed database in one
> command.  I am looking for something equivelant.
>
> Thank you for any ideas.
>

I have a simple method that works fairly well for me. In one of the tables
(does not matther which, pick one), I use the user minor version to keep
track of the database  "version" (my version, not dbisam's). Then on the
datamodule I have a constant with the current version number. The new
releases include not only the new programs, but also SQL scripts that update
the tables - including changing the user minor version on my control table.

Then when the program starts, before I attempt to do any database activity
or even open any table, I compare the datamodule constant with the user
minor version on my control table and if they don't match then apply the
corresponding upgrades. To keep it simple, the upgrade files correspond to
the tables version (upgrade01.SQL upgrade02.SQL etc)

Robert

Thanks Robert.

Do you have some utiltity to help keep track of the data changes?  Or do you have a utility that will generate the sql scripts that will alter/create the tables?

DAN
Sun, May 9 2010 4:24 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Dan


Check out http://www.contextsoft.com/

Roy Lambert
Sun, May 9 2010 11:57 AMPermanent Link

Iztok Lajovic (1)

>>
Dan wrote:

I am looking at purchasing DBISAM and am wondering what is the best way to apply new data structures to existing installed applications.  For example, if an existing table has a new field or has a change to an existing field, do I have to keep track of all the modifications and then apply them via SQL queries?

I am using a lot of BDE -> Paradox tables currently.  I have a utility that uses the dbi functionality in the bde unit.  IT allows me to export the table structures, indexes, and keys to a text file.  That text file can be parsed and the changes applied to the depolyed database in one command.  I am looking for something equivelant.

Thank you for any ideas.

DAN
>>

Dan,

checkout the discussion we had some time ago:
http://www.elevatesoft.com/forums?action=view&category=dbisam&id=dbisam_general&forum=DBISAM_Discussion#61790

Regards
Iztok Lajovic
Sun, May 9 2010 12:17 PMPermanent Link

Robert Kaplan


<Dan> wrote in message
news:98A6B9BE-4076-4BF3-94BF-A9A8886A3146@news.elevatesoft.com...
>
> Do you have some utiltity to help keep track of the data changes?  Or do
> you have a utility that will generate the sql scripts that will
> alter/create the tables?

If they are new tables, DBSYS has a reverse engineer capability that
generats the SQL. To do upgrades, I just do them by hand. It is the same SQL
that I would use to upgrade my tables.

As far as keeping track of the data changes, I do have documenttion, but it
is pretty much written by us. Never found a good data dictionary for DBISAM.

Robert

Image