Обсуждение: REF: Data Migration MS SQL Server 7.0 to PostgreSQL 8.4 on Linux
Good morning, 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 ....¡
From: bcld@hotmail.com
To: pgsql-es-ayuda@postgresql.org; vepug@postgresql.org; pgsql-admin@postgresql.org
Subject: REF : MIgracion de datos ms sql server 7.0 a Postgresql 8.4 en Linux
Date: Thu, 11 Feb 2010 12:58:46 +0000
Buenos dias, estoy en estos momentos en un proceso de migracion de una base de datos de un manejador ms sql server 7.0 a postgresql vesion 8.4 pero tengo un problema con un tipo de dato el (timestamp) que en sql server 7.0 se refiere a un campo binario unico que se actualiza en forma aleatoria por fila , y este campo es primordial en mi aplicacion para efectos del seguimiento, ahora en postgresql 8.4 tambien tengo el mismo timestamp pero se refiere a otro tipo de dato (fecha+hora ), he investigado otros tipo de datos tales como (serial, uuid,xid, bytea etc)en postgresql y no consigo algo igual para sustituirlo, he pensado en una funcion que realice algo parecido pero todavia no lo intento, y por supuesto recurro a ustedes para ver si me pueden echar una mano con este bache que tengo ahorita ....¡
Saludos
Luis Dominguez
Luis Dominguez <bcld@hotmail.com> 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
Hola Rafael.
You could generate a UUID. There is a contrib module in contrib/uuid-ossp with several functions in order to generate an UUID with different algorithms, as documentation says.
If you don’t want to use these functions because you use an specific format, perhaps they could serve you as example in order to create a custom one.
Espero haberte dado alguna idea.
De: Luis Dominguez [mailto:bcld@hotmail.com]
Enviado el: jueves, 11 de febrero de 2010 14:36
Para: pgsql-es-ayuda@postgresql.org; vepug@postgresql.org; pgsql-admin@postgresql.org
Asunto: [ADMIN] REF: Data Migration MS SQL Server 7.0 to PostgreSQL 8.4 on Linux
Good morning, 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 ....¡