Am 21.05.2010 03:46, schrieb Adrian Klaver:
You know serial is just a shortcut for:
pid int NOT NULL DEFAULT nextval('seq')
I think you will find Access will place nice if you use the long form to define
your autoincrement.
Not true. Serial will also add an internal dependency between the
> On Thu, May 20, 2010 at 5:52 PM, wrote:
>
>> I'm new to triggers in PostgreSQL. I have to create a trigger on insert
>> to
>> increment a sequence to overcome MS-Access' limitation in acknowledging
>> serial "datatype".
>
> Uh? Access doesn't need to acknowledge the serial datatype.
> At-least
> On Thursday 20 May 2010 5:53:51 pm tla...@gwdg.de wrote:
>> I'm new to triggers in PostgreSQL. I have to create a trigger on insert
>> to
>> increment a sequence to overcome MS-Access' limitation in acknowledging
>> serial "datatype".
>>
>
> You know serial is just a shortcut for:
>
> pid int NOT
On Thursday 20 May 2010 5:53:51 pm tla...@gwdg.de wrote:
> Hello all,
>
> I'm new to triggers in PostgreSQL. I have to create a trigger on insert to
> increment a sequence to overcome MS-Access' limitation in acknowledging
> serial "datatype".
>
> Could anyone put me on right track? I was looking t
Hello all,
I'm new to triggers in PostgreSQL. I have to create a trigger on insert to
increment a sequence to overcome MS-Access' limitation in acknowledging
serial "datatype".
Could anyone put me on right track? I was looking the whole day for
references on that... Years ago I quickly found a re
Joel Fradkin wrote:
Basically the question was why would a view use an indexed search on one
result set but a seq search on a larger result set. Same view only
difference is how many rows are returned. The large result set was doing a
seq search and did not return after several minutes. The same sq
Basically the question was why would a view use an indexed search on one
result set but a seq search on a larger result set. Same view only
difference is how many rows are returned. The large result set was doing a
seq search and did not return after several minutes. The same sql ran in 135
seconds
work for these settings).
Hope this helps,
Greg Williamson
DBA
GlobeXplorer LLC
-Original Message-
From: Javier Tesis Tolosa Trabajo [mailto:[EMAIL PROTECTED]
Sent: Wed 7/21/2004 8:08 AM
To: [EMAIL PROTECTED]
Cc:
Subject: [SQL] Sorry too many conecctions
hi everyb
hi everybody
I speak english a little,Sorry.
I have A problem whith de connections from a Aplicatio Java, guive me a
Error "Sorry too many clients",I think what is becuase I don't close
connecction to the DB postgresql, I do aprox. 1000 conecction into statement
"while" What can Do?
thakns
___
>
> When I'm trying to connect I have this error message:
>
> Something unusual has occured to cause the driver to
> fail.Please report this
> exception: java.sql.SQLException: Sorry, to many clients already.
>
I also met this error yesterday. Default PostgreSQL limit for incoming connections
On Mon, 2003-01-06 at 09:12, cristi wrote:
> When I'm trying to connect I have this error message:
>
> Something unusual has occured to cause the driver to fail.Please report this
> exception: java.sql.SQLException: Sorry, to many clients already.
>
>
> What should I do?
>
I might suggest post
When I'm trying to connect I have this error message:
Something unusual has occured to cause the driver to fail.Please report this
exception: java.sql.SQLException: Sorry, to many clients already.
What should I do?
---(end of broadcast)---
TIP 6
On Tue, Jul 16, 2002 at 12:37:04PM -0500, Kevin Brannen wrote:
> Josh Berkus wrote:
> > Christopher,
> >
> >
> >>In the bad old days when we couldn't distinguish explicit from implicit
> >>cast functions, I was wary of adding new cast pathways. Too many
> >>implicit casts and you have no type s
Kevin,
> In this vain, is there someplace in the docs that has a type conversion
> table (matrix) that shows what datatype can be cast into what other
> datatype (both implicitly and explicitly)? I haven't seen one and it
> would be helpful for us newbies.
I don't think it exists. Hey, ho
Josh Berkus wrote:
> Christopher,
>
>
>>In the bad old days when we couldn't distinguish explicit from implicit
>>cast functions, I was wary of adding new cast pathways. Too many
>>implicit casts and you have no type system at all. But in 7.3 there
>>should be no reason to object to an explici
Christopher,
> In the bad old days when we couldn't distinguish explicit from implicit
> cast functions, I was wary of adding new cast pathways. Too many
> implicit casts and you have no type system at all. But in 7.3 there
> should be no reason to object to an explicit-only cast from numeric
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> [ there's no cast from numeric to text ]
Feel free to contribute one.
In the bad old days when we couldn't distinguish explicit from implicit
cast functions, I was wary of adding new cast pathways. Too many
implicit casts and you have no t
Ignore previous half-completed email.
How do you get this to work in 7.2.1?
I'm creating a view of a table, but I'm trying to do something like
this:
create table t (
id integer not null,
amount numeric(7,2)
);
create view v as
select id as v_id,
'paid amount: ' || amount as v_comme
My spam filter was misconfigured and I bounced back some messages I
shouldn't have. Sorry.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your
19 matches
Mail list logo
