On Wednesday 07 January 2004 23:01, Michael Fuhr wrote:
> On Wed, Jan 07, 2004 at 07:47:32PM +0530, Kenneth Gonsalves wrote:
> > in 7.4 i'm getting an error message - UNIQUE constraint matching keys for
> > table 'xxx' not found - any clues?
>
> It would be helpful to see the *exact* wording of the
Rodrigo Sakai wrote:
> I did some importation from a .csv file to a table
>
> (this is a very small piece of the csv file, but i think its good for
> the exemple. the pipe "|" is the delimiter for this file)
> 001|002|3041300045027612|002
> 001|002|3041000218146611|002
> 001|002|3040600
Andreas wrote:
> Why can['t] we use INDEX the same way as UNIQUE ?
> Perhaps even as in
> ...
> numba INT4NOT NULLINDEX
> ...
If the choice were just index or no index, then this might be ok, but
when you create an index you can choose the index type, the operator
class, a partial in
On Wednesday 07 January 2004 17:09, Andreas wrote:
> Hi,
>
> I'm moving from MySQL to Pg.
> MySQL lets me create indices like this:
>
> CREATE TABLE t (
> id INTEGERNOT NULL,
> numba INTEGER NOT NULL,
> txtVARCHAR(100) NOT NULL,
> anosanumba INTEGER
Hi everyone, I need some help please
I did some importation from a .csv file to a table
(this is a very small piece of the csv file, but i think its good for
the exemple. the pipe "|" is the delimiter for this file)
001|002|3041300045027612|002
001|002|3041000218146611|002
001|002|30
On Wed, Jan 07, 2004 at 07:47:32PM +0530, Kenneth Gonsalves wrote:
> in 7.4 i'm getting an error message - UNIQUE constraint matching keys for
> table 'xxx' not found - any clues?
It would be helpful to see the *exact* wording of the error message and
the SQL statements that can be used to reprod
in 7.4 i'm getting an error message - UNIQUE constraint matching keys for
table 'xxx' not found - any clues?
--
regards
kg
http://www.ootygolfclub.org
poor man's tally: http://avsap.sourceforge.net
---(end of broadcast)---
TIP 9: the planner will
Hi,
I'm moving from MySQL to Pg.
MySQL lets me create indices like this:
CREATE TABLE t (
id INTEGERNOT NULL,
numba INTEGER NOT NULL,
txtVARCHAR(100) NOT NULL,
anosanumba INTEGER NOT NULL ,
PRIMARY KEY (id),
INDEX (numba),
UNIQUE (anosanumba)
);
Hi,
yes yes. U understood in a very correct way, as i have 2 tables -
appointments and recurrences. And we are not gonna use PHP.
For future dates, I am not gonna populate, instead I am gonna check for the
recurrences tables for ever appointments and based on the conditions, I am
gonna say how man
Hi all;
If I understand Kumar's post correctly, he is having some question relating
to the issue of even recurrance. I would highly suggest reading the
ICalendar RFC (RFC 2445) as it has some interesting ideas on the subject.
HERMES (my app with appointment/calendar functionality) doesn't yet sup
10 matches
Mail list logo