Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 7F6C063346B; Thu, 11 Feb 2010 11:06:49 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 50400-10; Thu, 11 Feb 2010 15:06:29 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id F16D5632D64; Thu, 11 Feb 2010 11:06:37 -0400 (AST) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Thu, 11 Feb 2010 09:06:35 -0600 Message-Id: <4B73C895020000250002F180@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Thu, 11 Feb 2010 09:06:29 -0600 From: "Kevin Grittner" To: "Luis Dominguez" , "pgsql-admin@postgresql.org" , "pgsql-es-ayuda@postgresql.org" , "vepug@postgresql.org" Subject: Re: REF: Data Migration MS SQL Server 7.0 to PostgreSQL 8.4 on Linux References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.724 tagged_above=-10 required=5 tests=AWL=-0.614, BAYES_05=-1.11 X-Spam-Level: X-Archive-Number: 201002/93 X-Sequence-Number: 33696 Luis Dominguez wrote: > I am now in the process of migrating a database from a driver > ms sql server 7.0 to postgresql 8.4 vesion but I have a problem > with the data type (timestamp) SQL Server 7.0 that refers to a > single binary field that is updated randomly by row, and this > field is paramount in my application for purposes of monitoring, > postgresql 8.4 now also have the same timestamp but refers to > other data (date + time), I investigated other types of data such > as (serial, uuid, xid, byte etc) in postgresql and not get > something just to replace it, I thought of a function that do > something similar but not yet tried, and of course I turn to you > to see if I can lend a hand with this rut that I have right now Did you consider creating a SEQUENCE used by a trigger on update or insert of a row? http://www.postgresql.org/docs/8.4/interactive/sql-createsequence.html -Kevin