X-Original-To: pgsql-novice-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7D6595367A for ; Mon, 18 Apr 2005 03:09:15 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 75069-06 for ; Mon, 18 Apr 2005 06:09:12 +0000 (GMT) Received: from themode.com (themode.com [161.58.169.198]) by svr1.postgresql.org (Postfix) with ESMTP id E6FB653661 for ; Mon, 18 Apr 2005 03:09:11 -0300 (ADT) Received: from localhost (bde@localhost) by themode.com (8.12.11/8.12.11) with ESMTP id j3I69BB3099068 for ; Mon, 18 Apr 2005 02:09:11 -0400 (EDT) Date: Mon, 18 Apr 2005 02:09:10 -0400 (EDT) From: brew@theMode.com X-X-Sender: mode@themode.com To: pgsql-novice@postgresql.org Subject: Storing Large Objects In-Reply-To: <70E6659A9338D8418379B4EC0CA5819137928D@erumomw002.eemea.ericsson.se> Message-ID: References: <70E6659A9338D8418379B4EC0CA5819137928D@erumomw002.eemea.ericsson.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.178 tagged_above=0 required=5 tests=NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200504/224 X-Sequence-Number: 13107 Hi All...... I'm writing a php web application which sells mp3 music for production use (a rather limited audience, as opposed to a general mp3 download site). Since I've heard large objects were a bother I've written it so the mp3s were in files with long obfuscated filenames and have put them in a directory hidden behind basic authentication, planning a php front end to the basic authentication and storing the file urls in the database. Now I'm considering shortlived symbolic filenames to further make it difficult to rip off the mp3 files by other users with valid log in credentials that can get past the basic authentication. Basically it's turning into one big unwieldy kluge. I'm reading about large object php functions and am considering storing the mp3s themselves as large objects in postgreSQL, rather than just the filenames, and it's starting to look better and better! It would be very easy to make it so that only the valid user could pull the mp3 large object out of postgreSQL. Is storing large objects as easy as the php functions make it look? What about the pg_dump difficulties with large objects? I'm using Debian Stable which has postgreSQL 7.2.1 and PHP 4.1.2 which so far has been working fine with my small text databases, but I suspect if I want to consider large objects I should really upgrade, eh? TIA.... brew ========================================================================== Strange Brew (brew@theMode.com) Check out my Stock Option Covered Call website http://www.callpix.com and my Musician's Online Database Exchange http://www.TheMode.com ==========================================================================