Skip site navigation (1) Skip section navigation (2)

Re: From SQLite to Postgres

From: "Eli Adam" <EAdam(at)co(dot)lincoln(dot)or(dot)us>
To: "Rich Shepard" <rshepard(at)appl-ecosys(dot)com>,<pdxpug(at)postgresql(dot)org>
Subject: Re: From SQLite to Postgres
Date: 2011-02-16 18:36:45
Message-ID: 4D5BA8BC.4F75.00CE.0@co.lincoln.or.us (view raw or flat)
Thread:
Lists: pdxpug
gdal/ogr may help you.  See supported vector formats here:
http://gdal.org/ogr/ogr_formats.html 

More SQLite and postgis here:

http://postgis.refractions.net/pipermail/postgis-users/2008-April/019225.html 



Bests, Eli

>>> On 2/16/2011 at 10:30 AM, in message
<alpine(dot)LNX(dot)2(dot)00(dot)1102161026320(dot)19529(at)salmo(dot)appl-ecosys(dot)com>, Rich Shepard
<rshepard(at)appl-ecosys(dot)com> wrote:
> On Wed, 16 Feb 2011, Brent Dombrowski wrote:
> 
>> I've gone from Access straight to postgres in the past. I set up an ODBC
>> connection from Access to postgres and just dragged and dropped the tables
>> across. The gotcha for me was name preservation from Access required
>> quoting all the field and table names in postgres. My tables were simple,
>> your mileage may vary.
> 
> Brent,
> 
>    Your approach requires access to Access. We don't do Microsoft. I suppose
> that I could read it into OO.o, but that seems to increase the potential for
> problems.
> 
>    Looking at the file in emacs (it's 88M, 110+k rows), I think I need to
> change the delimiter, drop the single quotes and the explicit NULLs, and
> clean up the empty spaces that sqlite puts in for constant length
> attributes. I'm not sure about the PRAGMA statement at the top of the file,
> or if postgres wants something different.
> 
> Thanks,
> 
> Rich
> 


In response to

Responses

pdxpug by date

Next:From: Rich ShepardDate: 2011-02-16 18:37:50
Subject: Re: From SQLite to Postgres
Previous:From: Rich ShepardDate: 2011-02-16 18:32:59
Subject: Re: From SQLite to Postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group