Sent: Dienstag, 11. Jänner 2005 15:50
> To: KÖPFERL Robert
> Cc: pgsql-sql@postgresql.org
> Subject: RE: [SQL] Single row tables
>
>
> I suppose you could put a check constraint that forces a
> single value on a column with a unique index? Or an insert
> trigger that alway
Thank you for this rather detailed example.
I already learned something and omitted a fault. There should be enogh to
implement such a Queue. :-)
> -Original Message-
> From: Andrew Hammond [mailto:[EMAIL PROTECTED]
> Sent: Mittwoch, 12. Jänner 2005 17:19
> To: KÖPFERL
- there's however just an
example for C. I don't want to engage the compiler :-/
> -Original Message-
> From: sad [mailto:[EMAIL PROTECTED]
> Sent: Mittwoch, 12. Jänner 2005 07:40
> To: KÖPFERL Robert
> Cc: pgsql-sql@postgresql.org
> Subject: Re: [SQL] Single row
> -Original Message-
> From: Andrew Sullivan [mailto:[EMAIL PROTECTED]
> Sent: Donnerstag, 13. Jänner 2005 20:49
> To: 'pgsql-sql@postgresql.org'
> Subject: Re: [SQL] Column with recycled sequence value
>
...
> > used 2^32 will be reached soon and then? There are far less
> than 4G-reco
hat you just
> started, and that means your new id's will be compactly
> arranged, starting
> at 1.
>
> - Update your existing table, joining it to the
> translate table, to
> replace the old id by the new id.
>
>
> > On Thu, Jan 13, 2005 at 06:08
I think don't really unterstand your intend.
However there exists a type text in SQL and Postgres which is a text of
unspecified length and used like a SQL-String. Thus quoted with '
So when you earlier were able to gain the content of that field. It should
be no problem to quote it.
> -Origi
Yo can do s.t. similar, if the order in which you select the columns
corresponds to the order your type is defined.
So you'd gonna use: select intcol, textcol from table;
> -Original Message-
> From: Din Adrian [mailto:[EMAIL PROTECTED]
> Sent: Montag, 17. Jänner 2005 13:31
> To: pgsql-sql
Did you try to
explicitly give the type for the literal?
e.g.
''::varchar
-Original Message-From:
Yudie [mailto:[EMAIL PROTECTED]Sent: Montag, 17. Jänner 2005
19:44To: pgsql-sql@postgresql.orgSubject: [SQL] query
configuration for validate empty quote to zero
We just changed
but
if you are looking for something you can find it in some example or
mentioned in a sentence somweheewere
> -Original Message-
> From: Michael Fuhr [mailto:[EMAIL PROTECTED]
> Sent: Dienstag, 18. Jänner 2005 19:52
> To: KÖPFERL Robert
> Cc: pgsql-sql@postgresql.org
> S
As so often, I would suggest regular languages to accomplish most of the
work that comes up.
Use for example ours all friend 'sed' to edit a big sql-dump.
you can for example simply replace isnull(X) by X is null.
RegEx will possibly not reach for all posibilities but the're very good for
the fir
TED]
> Sent: Mittwoch, 19. Jänner 2005 18:02
> To: KÖPFERL Robert
> Cc: pgsql-sql@postgresql.org
> Subject: Re: [SQL] Returning a bool on DELETE in a proc.
>
>
> On Wed, Jan 19, 2005 at 11:24:26AM +0100, KÖPFERL Robert wrote:
>
> > Seems that I forgot to mention that th
That's bad.
Is there really no ohter way?
So it takes TWO termoral tables. Or even more?
And it can't be just sql because theres more around that statement.
> -Original Message-
> From: Sean Davis [mailto:[EMAIL PROTECTED]
> Sent: Donnerstag, 27. Jänner 2005 14:57
&
This
seems more less rpm-related.
However: Already tried to uninstall the old
packages?
# man
rpm
-Original Message-From: Joel Fradkin
[mailto:[EMAIL PROTECTED]Sent: Samstag, 05. Februar 2005
23:36To: pgsql-sql@postgresql.orgSubject: [SQL]
postgres8 install on fedora core
Thanks.
I managed it via a trigger.
> -Original Message-
> From: Michael Fuhr [mailto:[EMAIL PROTECTED]
> Sent: Sonntag, 13. Februar 2005 02:57
> To: KÖPFERL Robert
> Cc: pgsql-sql@postgresql.org
> Subject: Re: [SQL] Constraint doesn't see a currently inserte
ANGUAGE 'c' VOLATILE;
CREATE TRUSTED PROCEDURAL LANGUAGE 'plpgsql'
HANDLER plpgsql_call_handler;
C:\> -Original Message-
C:\> From: Steve - DND [mailto:[EMAIL PROTECTED]
C:\> Sent: Donnerstag, 24. Februar 2005 18:41
C:\> To: KÖPFERL Robert; pgsql-sql@postgresql.
|-Original Message-
|From: Goulet, Dick [mailto:[EMAIL PROTECTED]
|Sent: Montag, 07. März 2005 16:33
|To: John DeSoi; Stef
|Cc: pgsql-ADMIN@postgresql.org; pgsql-sql@postgresql.org
|Subject: Re: [SQL] [ADMIN] Postgres schema comparison.
|
|
| My favorite for this task is WinSql available f
d.
This may mean that (as you asked) a select over a table function produces a
temprary table and thus costs much ressources if the table is big.
|-----Original Message-
|From: KÖPFERL Robert
|Sent: Montag, 14. März 2005 12:26
|To: pgsql-sql@postgresql.org
|Subject: [SQL] How does the planner t
ROTECTED]
|Sent: Mittwoch, 20. April 2005 23:06
|To: Tambet Matiisen
|Cc: KÖPFERL Robert; pgsql-sql@postgresql.org
|Subject: Re: [SQL] Function to either return one or all records
|
|
|"Tambet Matiisen" <[EMAIL PROTECTED]> writes:
|> Standard technique is to rewrite OR que
Thanks.
Since I was just interested in this special case (while the general wasn't
interesting, either) this helped me. Also psql -E is a nice new feature to
me.
|-Original Message-
|From: Michael Fuhr [mailto:[EMAIL PROTECTED]
|Sent: Montag, 30. Mai 2005 16:09
|To: KÖPFERL Rober
To me it seems that the definer of this table missed the concept index ...
or the concept database
One usually looks up data using a key, but if the whole row is the key, what
data shall be looked up.
So short story long: Remove data from your index. The data column seems
like the data to be look
Can
please some of the administrators remove that member or
what-o-else
-Original Message-From: AntiSpam UOL
[mailto:[EMAIL PROTECTED]Sent: Dienstag, 07. Juni 2005
11:22To: KÖPFERL RobertSubject: RE: Re: [SQL] SQL
equivalent to nested loop
ANTISPAM UOL »
Hello,
I have seen in another thread that sub-queries in a CHECK constraint
have implementation ramifications that make them awkward to implement and
support. OK, fair enough, c'est la vie.
ERROR: cannot use subquery in check constraint
is the result. I have a model which seems to BE
FROM master m, slave s
WHERE m.m_id = s.m_id (+);
m_id | m_name | m_id | s_name
--++--+---
1 | Satan |1 | Joe
1 | Satan |1 | Tom
2 | God| |
(3 rows)
I keep a file at http://comptechnews.com/~reaster/dbdesign.html that has
some info that might be useful to some people.
--
Robert B. Easter
ION miFunc () RETURNS OPAQUE AS '
>DECLARE
> Cuenta_t INT4;
>BEGIN
> begin work;
Can't have nested transactions. Can't use BEGIN/COMMIT within a trigger.
--
Robert B. Easter
numbers?
>
> Michael Lea
> Information Security
> Manitoba Public Insurance
> Phone: (204) 985-8224
--
Robert B. Easter
;
--
Robert
to get it.
--
- Robert
en
-- you make a trigger handle more than just INSERT
IF NEW.publishtime NOTNULL THEN
INSERT INTO news_unpublished VALUES (NEW.id);
END IF;
RETURN NEW;
END IF;
' LANGUAGE 'plpgsql';
CREATE TRIGGER newstrigger
AFTER INSERT ON news FOR EACH ROW
EXECUTE PROCEDURE news_trigproc();
--
- Robert
On Thu, 27 Jul 2000, Robert B. Easter wrote:
> On Thu, 27 Jul 2000, André Næss wrote:
> > I've been looking through the material I have on postgreSQL, but can't seem
> > to find an answer to my problem. Very simplied, my tables are something like
> > this:
> &g
doing but by having your
own triggers do it, you have control of the order of how things happen on
delete.
>
> I also find it rather inelegant to use the constraint to handle DELETE
> operations on news, whereas UPDATEs and INSERTs are handled by the trigger
> procedure. Somehow I would like to either do all the tasks using the trigger
> procedure, or using rules.
>
> As for Itai Zukerman's comment: AOL. Good resources around triggers and
> rules are very much needed!
>
> Regards
> André Næss
--
- Robert
e to maintain all the scripts. With the trigger procs, the
logic is implemented in one central place where no php scripts etc can
circumvent the rules/logic in the triggers.
PHP can provide a first level check that things are done right, but the trigger
procs in the database can provide the final check.
--
- Robert
i'm reading the postgres documentation and i'm specifically
interested in creating stored procedures so that i can keep
as much of the business logic in the database as possible.
while reading 13.1.3 (SQL Functions on Composite Types) in
the Programmer's Guide i come across the phrase...
"When
you can't.
rjsjr
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Joseph Syjuco
> Sent: Tuesday, August 14, 2001 10:34 PM
> To: [EMAIL PROTECTED]
> Subject: [SQL] user defined function question
>
>
> how do i return a resultset from a user defined
i'm fairly new at this whole database design thing and my grasp of set
theory is not what it was when i was in college lo these many years
past. but i want to get a better idea of how to optimize sql
statements.
i have several friends that are DBA's by profession and work on oracle
and/or ms sql
My office is working on a fantasy football database and, unfortunately, I
have been tagged as the DBA. I'm a bit weak on set theory but I'm trying.
Right now I am trying to calculate up game scores into the database rather
than running through code to do that. A baseline of my schema is that:
+ E
201 - 235 of 235 matches
Mail list logo