Re: [SQL] how to add primary key to existing table with multiple primary keys

Your table has a primary key yet, so you can´t add a second primary key.  You only can define one pk, however it can be composed as your table has (it now has 2 columns), so I think you need to drop the current pk and add again the new pk with your 3 columns (probeid, tissueid, expid).   Rev

Re: [SQL] Slow update SQL

 You can try this too:...WHERE EXTRACT(YEAR FROM dxdate::Date) > 2000 Mauricio Fernández A.Ingeniero de SistemasUniversidad Autónoma de Manizales (Colombia) -Mensaje original-De: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED]]En nombre de Bungsuputra LinanEnviado el: lunes, 27 febrero, 2

Re: [SQL] Unable to identify an ordering operator '<' for type 'smallint[]'

I get the result expected Thanks for your help Mauricio Fernández A. Ingeniero de Sistemas U. Autónoma de Manizales -Mensaje original- De: Tom Lane [mailto:[EMAIL PROTECTED] Enviado el: miércoles, 11 enero, 2006 19:25 Para: Mauricio Fernandez A. CC: pgsql-sql@postgresql.org Asunto: Re: [SQL]

[SQL] Unable to identify an ordering operator '<' for type 'smallint[]'

Hello I have been working in a report based on the query bellow. It works fine in my development server which is postgres 8.0 but in production I have postgres 7.3 and I am getting the following error: SQL Error : ERROR: Unable to identify an ordering operator '<' for type 'smallint[]' U

[SQL] Anual Query

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Can any of you help me with this query?, I need to retrieve the sum(units) and sum(cost) for each client in every month in the same row, something like this: client|UnJan|CostJan|UnFeb|CostFeb|UnMar|CostMar ...|UnDec|CostDec - -

[SQL] does indexes need statistics?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everybody, Is it necesary the statistics be enabled when I create indexes or to use them? thanks Mauricio Fernández A. Ingeniero de Sistemas U. Autónoma de Manizales -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.0.2i iQA/AwUBQ4X7u84irm

Re: [SQL] Como ejecutar una funcion insert en plpgsql....

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fernando lo que pasa es que postgres siempre pasa a minusculas los nombres de los campos o tablas excepto si estos se escriben entre comillas. es decir algo como: select CAMPO1 ... postrgres lo pasara a: select campo1 .. y algo como select "CamPo

[SQL] Character set error

Good Day. I´m working with postgres 7.4. on Win XP and when I do a query like select* from table it returns me this error message: Invalid character data was found. This is most likely caused by stored data containing characters that are invalid for the character set the database was created in