[pycsw-devel] PyCSW record copying

[Dan Ramage]

Angelos, 

Thanks for the feedback. They will be the same POSTGIS and PostGres
versions, the databases reside on the same machine.

Dan

From:  Angelos Tzotsos <gcpp.kalxas at gmail.com>
Date:  Mon, 10 Nov 2014 21:26:08 +0200
To:  <pycsw-devel at lists.osgeo.org>
Subject:  Re: [pycsw-devel] PyCSW record copying

    
 
Hi Dan,
 
 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.
 
 Cheers,
 Angelos
 
 On 11/10/2014 08:47 PM, Dan Ramage wrote:
 
 
>  
> 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
> 
> 
> 
>  
>   
>  
> _______________________________________________
> pycsw-devel mailing list
> pycsw-devel at lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/pycsw-devel
>  
 
 
 
-- 
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
http://users.ntua.gr/tzotsos
 
_______________________________________________ pycsw-devel mailing list
pycsw-devel at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pycsw-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pycsw-devel/attachments/20141110/2eb5297a/attachment.html>