Subject | Re: [ib-support] Re: Syncronizing Databases |
---|---|
Author | hans@hoogstraat.ca |
Post date | 2001-08-13T20:38:10Z |
A simple loop like this pump 1000nd's of records/sec for me,
but Jason one time mentioned an even faster way with some simple
assign I believe.
IB_Query.SQL.Text = 'select * from TableTo for update';
........
IB_Query.Append;
for i := 0 to Table.FieldCount -1 do
begin
FieldFrom := Table.Fields[i].FieldName;
FieldTo := FieldFrom;
....
do some editing or conditional cheches if required
....
IB_Query[FieldTo] := Table[FieldFrom];
end;
IB_Query.Post;
===========================================================
Todd Brasseur wrote:
but Jason one time mentioned an even faster way with some simple
assign I believe.
IB_Query.SQL.Text = 'select * from TableTo for update';
........
IB_Query.Append;
for i := 0 to Table.FieldCount -1 do
begin
FieldFrom := Table.Fields[i].FieldName;
FieldTo := FieldFrom;
....
do some editing or conditional cheches if required
....
IB_Query[FieldTo] := Table[FieldFrom];
end;
IB_Query.Post;
===========================================================
Todd Brasseur wrote:
>
> This would definitely be the easiest way. The problem is that there
> is quite a bit of data and it would take to long to 'pump it'.
>
> Todd
>
> --- In ib-support@y..., hans@h... wrote:
> > Hello Todd,
> >
> > What I used to do is rename the current Clients DataBase.gdb
> > Install new empty database.
> > Wrote simple program or button on actual program
> > to pump from Client's renamed to new Empty Database.
> >
> > Always had a copy of Clients database this way.
> >
> > Probably better ways nowadays, but it worked for me :)
> >
> > Best regards
> > Hans
> >
> > ============================================================
> >
> > Todd Brasseur wrote:
> > >
> > > We are trying to decide how to handle keeping our clients databases
> > > metadata the same as ours.
> > >
> > > We have a production database in our office which we are continually
> > > changing as our product evolves. Our clients have their own copies of
> > > the database with their data.
> > >
> > > Every once in a while, we give them a new 'release of the software'
> > > which includes the new program along with updates to the database. We
> > > are finding it quite alot of work to maintain 'change scripts' to run
> > > against our clients databases. The most work is in keeping track of
> > > which scripts have been run against which clients databases.
> > >
> > > Does anyone have a similiar situation? Any ideas regarding how to
> > > manage the database changes would be greatly appreciated.
> > >
> > > Todd Brasseur
> > > COMPASS Municipal Services Inc.
> > >
> > > To unsubscribe from this group, send an email to:
> > > ib-support-unsubscribe@egroups.com
> > >
> > >
> > >
> > > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/