<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Dan,<br>
<br>
There is no limitation in doing a direct database copy, it is not
advertized because most users won't (and probably shouldn't) touch
the database directly. Just be cautious about database versions
and spatial extensions used (postgis). I recommend that those
should be in same versions.<br>
<br>
Cheers,<br>
Angelos<br>
<br>
On 11/10/2014 08:47 PM, Dan Ramage wrote:<br>
</div>
<blockquote cite="mid:D0867281.23459%25dan@inlet.geol.sc.edu"
type="cite">
<pre wrap="">I've got a "staging" pycsw server setup that I am using for bringing in
records from NDBC via SOS as well as other large providers. I then cull out
records that are not in my area of interest.
I know I can export those via pycsw-admin, but I was curious if that
provided any benefit, aside from creating the XML files, compared to doing a
database to database copy. Basically take the remaining records from the
staging database and copy them into the working database.
Dan
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
pycsw-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pycsw-devel@lists.osgeo.org">pycsw-devel@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/pycsw-devel">http://lists.osgeo.org/mailman/listinfo/pycsw-devel</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a></pre>
</body>
</html>