At 04:00 AM 15/08/2007, you wrote:
>Hello all!
>
>I have a program run under Windows, and it works fine.
>I use VS2005 and Firebird .NET Data Provider.
>The Server is Windows Server 2003 and the clients are WXP.
>I am using .net Compact Framework 2 sp 2 with FirebirdClient-1.5.2 to access
>FireBird 1.5 SS.
>
>I would like to change the Server to Linux.
>The same code, will it work ?
In principle, it can. On the whole this is not a .NET provider
issue at all, provided your application code and databases have been
created with interoperability in sight. However, if you hard-coded
file paths into your application, or used Full settings for
configuring the server's access to things like UDFs, or if you
defined external tables in your database, you will have to do some changes.
Except for external tables, all of the other changes will keep your
application workable on Windows, too. You would just use a different
firebird.conf file for each host environment.
In summary: a database alias should be used for the database file
path and your apps should always use the alias. All configurations
that access external objects (UDFs, blob filters, etc.) should be
RESTRICT or NONE, with the hard paths configured in
firebird.conf. The server's hostname should be made configurable by
the client (by a Registry setting or .ini file, or by user input).
If you have any UDFs or blob filters declared in the database, fix up
the issues before you back up the database for transportation. (And
do make sure that a version of your UDF is actually available for Linux!)
As for external tables, you should drop them from the database before
you back up ready for transporting. You can recreate them with a
script once you have ported the database and created a location on
the Linux server for them.
Helen
|
