Hi Stephen<div><br class="webkit-block-placeholder"></div><div>That's a good point. The way I've got things setup right now is that the files are first uploaded to a temp location and are then parsed into postgresql/postgis. I need to look into what you're suggesting and it's obviously a more efficient way of achieving the same result. Thanks,
</div><div><br class="webkit-block-placeholder"></div><div>Chetan<br><br><div><span class="gmail_quote">On 7/4/07, <b class="gmail_sendername">Stephen Frost</b> <<a href="mailto:sfrost@snowman.net">sfrost@snowman.net</a>
> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">* Chetan Tiwari (<a href="mailto:chetan.tiwari@gmail.com">chetan.tiwari@gmail.com</a>) wrote:
<br>> I have a little perl script that reads CSV files uploaded via a browser and<br>> inserts the data into a table in postgres. I'll be happy to share that with<br>> you. It's setup to run with active perl and apache on windows, but it would
<br>> be fairly easy to tweak it to your system setup.<br><br>If you want to do it on-the-fly you can use CGI.pm and its upload-hook<br>to avoid any disk i/o on the web server (and avoid any temp file<br>creation, or limits due to space on the disk, etc).
<br><br> Thanks,<br><br> Stephen<br><br></blockquote></div></div>