Changes for page Database Compatibility and Comparisons-FrontBase

Last modified by John Huss on 2010/07/23 14:35

From version 5.1

edited by John Huss
on 2010/07/23 14:32

Change comment: There is no comment for this version

To version 6.1

edited by John Huss
on 2010/07/23 14:34

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -124,7 +124,7 @@
  There are a few caveats with this backup:
 . FrontBase's delimited export doesn't do any quoting or escaping as far as I know.  The script above handles embedded quotes, but that is all.  So if your data has embedded line breaks, tabs, or double-quotes, then you will need to manually deal with that.  The easiest way is to just edit the data in the DB before backing up.  First run a query to escape double quotes so that " becomes "".  Then run a query to surround the data with double quotes.  These changes will make the export file valid but won't alter the data once it's imported.
--1. FrontBase's export padding CHAR (fixed-length) fields with zero bytes (0x0) which are not allowed by Postgres' import.  You can alter your schema to use VARCHAR instead before exporting, or just strip the zero bytes if you know that if won't mess up any other data you have.  You can strip them after exporting by running this command:
++1. FrontBase's export pads CHAR (fixed-length) fields with zero bytes (0x0) which are not allowed by Postgres' import.  You can alter your schema to use VARCHAR instead before exporting, or just strip the zero bytes if you know that if won't mess up any other data you have.  You can strip them after exporting by running this command:
  {{code}}