Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Data replication to PostgreSQL
From: Scott Mead <scottm@openscg.com>
In-Reply-To: 
 <CAGb7rSFg6yrriDsFrwgS1ECsO9fbDxWssbfxidXjo2TQStN4HQ@mail.gmail.com>
Date: Thu, 29 Dec 2016 12:28:38 -0500
Cc: pgsql-admin@postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFA4857A-7BC7-4AF4-90B4-D91AC1605764@openscg.com>
References: 
 <CAGb7rSFg6yrriDsFrwgS1ECsO9fbDxWssbfxidXjo2TQStN4HQ@mail.gmail.com>
To: Ram DBA <postgresdbas@gmail.com>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org


> On Dec 29, 2016, at 09:35, Ram DBA <postgresdbas@gmail.com> wrote:
>=20
> Hi team,
>=20
> We have an use case to copy the data from Salesforce to PostgreSQL enviro=
nment but because of DDL changes that can happen to tables from Salesforce =
application side, replication would eventually fail. Do we have any open so=
urce tools that can also capture the DDL changes and replicate to PostgreSQ=
L?

Are you using an export tool provided by salesforce, or a custom tool again=
st their APIs?=20=20

  Either way, you don't have access to their database, you should be dumpin=
g the data to a CSV and importing the CSV to postgres. It's been a while si=
nce I've monkeyed with it, There may be a new way of doing this, but I doub=
t it. As long as your export tool always creates a csv in the right format,=
 you'll be fine. If you aren't ordering your columns or are using *, you'll=
 never get a good read. Use the toon or API to create a consistent file eac=
h time in some standard format and you'll be as okay as possible.=20

--
Scott Mead via mobile
Skype  : scottm.openscg
Gtalk    : scottm@openscg.com

>=20
> Thank you in advance,
> Ram


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin