Hello!
using now() to init TIMESTAMP fields I got resolution of one second. How
can I define DEFAULT in column (TIMESTAMP type) to get higher
time-resolution (TIMESTAMP supports microseconds).
Please CC the answer to me.
--
radoslaw.stachowiak.http://alt
Radoslaw Stachowiak <[EMAIL PROTECTED]> writes:
> using now() to init TIMESTAMP fields I got resolution of one second. How
> can I define DEFAULT in column (TIMESTAMP type) to get higher
> time-resolution (TIMESTAMP supports microseconds).
You could make a variant of now() that relies on gettimeo
Tom, Stephan, Jan, Etc.
Can you help me with this one? I can't figure out what is meant by
this error message:
I have a long, complicated PL/pgSQL function called
fn_modify_candidates(INT4,INT4,INT4).
When I call:
SELECT fn_modify_candidate(1004,5,278417036)
I get:
ERROR: unexpected
Does the function have any SELECTs that aren't
SELECT INTOs?
On Tue, 20 Feb 2001, Josh Berkus wrote:
> Tom, Stephan, Jan, Etc.
>
> Can you help me with this one? I can't figure out what is meant by
> this error message:
>
> I have a long, complicated PL/pgSQL function called
> fn_modif
Tom, Stephan,
> Josh Berkus <[EMAIL PROTECTED]> writes:
> > ERROR: unexpected SELECT query in exec_stmt_execsql()
>
> plpgsql doesn't think you should execute bare SELECTs, only SELECT INTO.
That would explain it. I have a nested function call in the form:
SELECT fn_remove_lock(record_id, us
Josh Berkus <[EMAIL PROTECTED]> writes:
> ERROR: unexpected SELECT query in exec_stmt_execsql()
plpgsql doesn't think you should execute bare SELECTs, only SELECT INTO.
On reflection this seems an overly anal-retentive restriction, since
there are cases where one might execute a SELECT for its
Hi,
Does anyone know how postgres/ postmaster handles the
situation where the physical hard disk space is full ?
Does it crash / corrupt the database, or does it
cleanly exit with appopriate message so that relevant
tables can be pruned (by the user) to free up disk
space and get it working again
Thanks ! I'm using JDBC to insert into the tables.
Would it throw an SQLException in such a situation ?
Rini
--- "Diehl, Jeffrey" <[EMAIL PROTECTED]> wrote:
> I happen to know this very well... It handles
> things very gracefully as far
> as I can tell. I complains that it can't extend the
> t
On Wed, Feb 21, 2001 at 12:30:51PM +0900, Chris Czeyka wrote:
[big snip]
> of course I get the ERROR, that admin_t doesn't exist. So? help the stupid!
> pls!
I think the general idea is to create the tables first without the
constraints and then do ALTER TABLE ADD CONSTRAINT afterwards.
HTH,
Hey to all,
I got two tables, linked to each other. How can I tell the first CREATE TABLE
(institute_t) to wait to check the foreign key for the second table??? just
like "hold on a little bit... you'll receive your admin_t" :-) ? I thoght
DEFERRABLE, DEFERRED and transaction with BEGIN/COMMIT ta
ThX Kirby, ThX Martijn,
as you can see I'm new to the SQL- and database world.
My policy for this project is to FORCE an admin to be in an institute. If one
admin behaves bad for the database project the institute is responsible for
her/him. This institute would be represented by a special admin
You have to use ALTER TABLE to add the constraint to one of the tables.
Deferred refers to the checking of the constraint itself, not really
to the check to see if the table is there.
On Wed, 21 Feb 2001, Chris Czeyka wrote:
> Hey to all,
>
> I got two tables, linked to each other. How can I t
12 matches
Mail list logo