Re: image storing
От | Adam Lang |
---|---|
Тема | Re: image storing |
Дата | |
Msg-id | 00f701c02fc1$d9bb53a0$330a0a0a@6014cwpza006 обсуждение исходный текст |
Ответ на | Re: image storing (<bmccoy@chapelperilous.net>) |
Ответы |
Re: image storing
|
Список | pgsql-general |
Yeah, that is what I was thinking... except I would like to keep the existing Access front end... And the front end displays the pathnames as a "hyperlink" data type. I figure I'll have to change that to a string... just not sure how to keep it so they can just "click" on it and display the file. Adam Lang Systems Engineer Rutgers Casualty Insurance Company ----- Original Message ----- From: <bmccoy@chapelperilous.net> To: "Adam Lang" <aalang@rutgersinsurance.com> Cc: "PGSQL General" <pgsql-general@postgresql.org> Sent: Friday, October 06, 2000 2:09 PM Subject: Re: [GENERAL] image storing > On Fri, 6 Oct 2000, Adam Lang wrote: > > > Has anyone setup a postgres server that stores the location of images (or > > any file) and is accessed by a windows based client? In particular postgres > > running on a non-windows OS. > > Yes, but the access was via a web browser interface. I just stored the > pathnames in the database. I had postgres running on a Linux box, and the > images themseleves were on a RAID served through Novell, then converted > into PDF images and stored on another RAID served through Linux. If you > set up Samba, you could still get to the images even if they were on a > Linux box, but the web browse interface (using Perl as the development > langauge) was by far the easier to use for building an application. > > Brett W. McCoy > http://www.chapelperilous.net > -------------------------------------------------------------------------- - > design, v.: > What you regret not doing later on.
В списке pgsql-general по дате отправления: