经验证/推荐的将应用程序从FIB +迁移到Fire-DAC组件的方法 [英] Proven/recommended way to migrate application from FIB+ to Fire-DAC components

查看:79
本文介绍了经验证/推荐的将应用程序从FIB +迁移到Fire-DAC组件的方法的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在将大量具有FIB +硬连接内部连接的应用程序迁移到Fire-Dac组件中,我正在寻找一些最轻松的方法,该怎么做。

I'm migrating a large family of applications having hardwired FIB+ connectivity inside to Fire-Dac components and I'm looking for some least painfull way, how to do it.

首先,我对后端进行了分离和迁移,以使连接中立和连接依赖部分得以实现,并手动重构了现有应用程序。我也写过FireDac零件。

First, I've decoupled and migrated the backend to get connectivity neutral and connectivity dependend parts and refactored existing applications manually. I've written FireDac parts as well.

要迁移Delphi代码似乎没问题...

To migrate Delphi code it seems to be no problem...

但是最大的麻烦似乎是在设计时迁移了放置在表单和数据模块上的组件:我安装了GExpert并尝试了其命令使用定义的规则替换组件来映射某些属性,但是组件之间却失去了相互引用

But big pain in the ass seems to be a migration of components placed on forms and data modules in design time: I installed GExpert and tried its command Replace Components with defined rules how to map some properties, but it lost mutual reference between components, probably due type incompatibility in step-by-step replacing process.

我目前的做法是手工工作:在旧的FIB +组件的名称后添加后缀copy&将原始名称粘贴到新的相应Fire-Dac组件中。我对所有组件重复此步骤,然后正确设置属性并删除FIB +组件。它使我可以在此过程中一次又一次地检查旧设置。

My current approach is hand job: to add a suffix to the name of old FIB+ component, copy&paste original name to new corresponding Fire-Dac component. This step I repeat for all components, then set properties properly and drop FIB+ components. It allows me to inspect old setting again and again during this process.

有人有行之有效的推荐方法吗?

Does anybody has some proven/recommended way how to do it better?

谢谢,pf

推荐答案

几个方面:


  1. 如果对不同的SQL操作使用属性,则可以从FireDAC TADQuery派生TMyQuery。 TMyQuery将创建TADUpdateSQL并将其XxxxSQL属性发布在TMyQuery界面中。此外,您可以在TMyQuery中引入FireDAC TADQuery中缺少的其他FIBPlus属性和方法。

  2. 可以将类似的方法用于其他FIBPlus组件,以实现FireDAC和FIBPlus之间的高兼容性。 / li>
  3. 您可以使用FireDAC附加工具-ADDFMChanger自动执行从FIBPlus到FireDAC的PAS / DFM迁移。然后,设置和迁移将类似于 BDE-> FireDAC迁移。您可以从 da-soft.com 下载FireDAC / AnyDAC插件。
  4. >
  5. 主要的迁移问题可能是FireDAC / FIBPlus行为不同。我无法在此发表评论,因为我没有使用FIBPlus的经验。

  1. If you are using properties for different SQL operations, then you can derive TMyQuery from FireDAC TADQuery. TMyQuery will create TADUpdateSQL and publish it XxxxSQL properties in TMyQuery interface. Also, you can introduce in TMyQuery other FIBPlus properties and methods, missed in FireDAC TADQuery.
  2. The similar approach you can use for other FIBPlus components to achieve high compatibility level between FireDAC and FIBPlus.
  3. You can use FireDAC addon tool - ADDFMChanger, to automate PAS / DFM migration from FIBPlus to FireDAC. The setup and migration then will be similar to BDE -> FireDAC migration. FireDAC / AnyDAC addons you can download from da-soft.com.
  4. The major migration issue may be difference in FireDAC / FIBPlus behaviours. I cannot comment here, because I have no experience with FIBPlus.

这篇关于经验证/推荐的将应用程序从FIB +迁移到Fire-DAC组件的方法的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆