I asked them about the architecture independence point actually...
Here's the reply they gave:
"We did look into making the database and backup files binary
compatible across different endian platforms a while back.
We concluded that the implementation would be "very" non-trivial and
introduce a performance hit on one platform due
to a large amount of byte swapping. But since the PPC platform is
dead the advantage gained by this feature will diminish.
Therefore putting the required manpower into this does not make much
since."
F
On Aug 10, 2008, at 23:15, Mike Schrag wrote:
1. The resulting script.sql uses absolute pathnames for data files
This one drives me crazy, though a perl -pi -e can fix it pretty
easily.
2. If anything relevant already exists in the db the script will fail
Both can be worked around, but it makes the process more tedious
then just reverting to a backup. I will keep the points you make
in mind though.
.. and also I THINK that the ascii dump is not transaction-safe
like "write backup" is. I've never understood why FB doesn't
either write an architecture independent backup format or at the
very least support reading in both architectures in the event that
writing architecture independent is too expensive. I would LOVE to
just have a mysql-style SQL script dump format (that is transaction
safe). I'm sure they have good reasons why they didn't but it
would be really nice.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/flor385%
40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
