From bhatia_sunit@hotmail.com Thu Jun 4 14:00:23 2026 Received: from hotmail.com (f122.law4.hotmail.com [216.33.149.122]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f721Lsf62435 for ; Wed, 1 Aug 2001 21:21:54 -0400 (EDT) (envelope-from bhatia_sunit@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 1 Aug 2001 18:21:40 -0700 Received: from 66.35.212.35 by lw4fd.law4.hotmail.msn.com with HTTP; Thu, 02 Aug 2001 01:21:40 GMT X-Originating-IP: [66.35.212.35] From: "Sunit Bhatia" To: pgsql-general@postgresql.org Subject: Data Versioning Date: Thu, 02 Aug 2001 01:21:40 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 02 Aug 2001 01:21:40.0747 (UTC) FILETIME=[7BAD25B0:01C11AF1] X-Archive-Number: 200108/28 X-Sequence-Number: 13248 Does any body know if pgsql supports any kind of versioning of binary objects or data. e.g. If I'm storing a binary file in a row of a table, I would want to see different versions of the same biary file. Everytime I do a write, the version number should be bumped up !! Is it possible to do it in pgsql or any other databases. I'm using JDBC for connecting to database. thanks _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp From bhatia_sunit@hotmail.com Thu Jun 4 14:00:25 2026 Received: from hotmail.com (f41.law4.hotmail.com [216.33.149.41]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f720vSf51476 for ; Wed, 1 Aug 2001 20:57:28 -0400 (EDT) (envelope-from bhatia_sunit@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 1 Aug 2001 17:57:21 -0700 Received: from 66.35.212.35 by lw4fd.law4.hotmail.msn.com with HTTP; Thu, 02 Aug 2001 00:57:21 GMT X-Originating-IP: [66.35.212.35] From: "Sunit Bhatia" To: pgsql-general@postgresql.org Subject: Data Versioning Date: Thu, 02 Aug 2001 00:57:21 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 02 Aug 2001 00:57:21.0833 (UTC) FILETIME=[16188990:01C11AEE] X-Archive-Number: 200108/27 X-Sequence-Number: 13247
Does any body know if pgsql supports any kind of versioning of  binary objects or data. e.g. If I'm storing a binary file in a row of a table, I would want to see different versions of the same biary file. Everytime I do a write, the version number should be bumped up !!
 
Is it possible to do it in pgsql or any other databases.
I'm using JDBC for connecting to database.
 
thanks

Get your FREE download of MSN Explorer at http://explorer.msn.com
From yasuo_ohgaki@hotmail.com Thu Jun 4 14:00:23 2026 Received: from hotmail.com (oe42.law8.hotmail.com [216.33.240.100]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f722ENf75611 for ; Wed, 1 Aug 2001 22:14:23 -0400 (EDT) (envelope-from yasuo_ohgaki@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 1 Aug 2001 19:14:12 -0700 X-Originating-IP: [210.154.73.126] From: "Yasuo Ohgaki" To: "Sunit Bhatia" Cc: References: Subject: Re: Data Versioning Date: Thu, 2 Aug 2001 11:13:01 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: X-OriginalArrivalTime: 02 Aug 2001 02:14:12.0592 (UTC) FILETIME=[D2528700:01C11AF8] X-Archive-Number: 200108/31 X-Sequence-Number: 13251 > Does any body know if pgsql supports any kind of versioning of binary > objects or data. e.g. If I'm storing a binary file in a row of a table, I > would want to see different versions of the same biary file. Everytime I do > a write, the version number should be bumped up !! With PostgreSQL, you can create RULE to keep old values. (Much easier than other DB, thanks to RULE) Refer to PostgreSQL manual for details. Yasuo Ohgaki From barry@xythos.com Thu Jun 4 14:00:23 2026 Received: from barry.xythos.com (h-64-105-36-191.snvacaid.covad.net [64.105.36.191]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f722nZf84623; Wed, 1 Aug 2001 22:49:36 -0400 (EDT) (envelope-from barry@xythos.com) Received: from xythos.com (localhost.localdomain [127.0.0.1]) by barry.xythos.com (8.11.2/8.11.2) with ESMTP id f722knu03078; Wed, 1 Aug 2001 19:46:49 -0700 Message-ID: <3B68BF19.3020306@xythos.com> Date: Wed, 01 Aug 2001 19:46:49 -0700 From: Barry Lind User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010628 X-Accept-Language: en-us MIME-Version: 1.0 To: Sunit Bhatia CC: pgsql-general@postgresql.org, pgsql-jdbc@postgresql.org Subject: Re: Data Versioning References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200108/32 X-Sequence-Number: 13252 You should be able to easily design a database schema that does what you want. For example two tables, files ------ file_id (PK) file_name text ... file_versions ------------- file_version_id (PK) file_id (FK to files.file_id) version integer not null data oid not null ... Then when your application creates a new file you would insert a row into both the files and file_versions table. When your application 'updates' a file it just inserts into the file_versions table the new version. There is no explicit support for what you are trying to do native, and I don't know of any other databases that support that type of functionality either (at least I know Oracle does not). thanks, --Barry Sunit Bhatia wrote: > Does any body know if pgsql supports any kind of versioning of binary > objects or data. e.g. If I'm storing a binary file in a row of a table, > I would want to see different versions of the same biary file. Everytime > I do a write, the version number should be bumped up !! > > Is it possible to do it in pgsql or any other databases. > I'm using JDBC for connecting to database. > > thanks > > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >