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
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
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]
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
-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
- -
-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
-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
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
then 'Implicit cast for expressions and assignments'
else 'Implicit cast only for assignments'
end)
end ) as casttype
from pg_cast c, pg_type t, pg_type t1, pg_proc p
where c.castsource = t.oid and
c.casttarget = t1.oid a
CTED] [mailto:[EMAIL PROTECTED]
Enviado el: martes, 12 de julio de 2005 13:35
Para: Mauricio Fernandez
CC: pgsql-sql@postgresql.org
Asunto: Re: [SQL] PostgreSQL - ERROR: Cannot cast type character varying to
integer
Under PostgreSQL 7.3 it was necessary
to use an intermediate cast to text
when co
Hello I´m new in the list, and I want to learn a lot about postgresql, now
I´m working in a database and I have this problem:
I have a table called historicoventas as follows (just the structure)
> historicoventas
> (
> codigopedidovarchar(20)
> codigohospital
11 matches
Mail list logo