[SQL] query/transaction history/logs

[q]

Is there anyway we can track queries entered?
Is there a table that stores all the actions that a user entered? (history)
Is there such a feature?


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[SQL] graphical interface - admin

[q u a d r a]

What's the best open source GUI for DB administration? (postgres)




---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

[SQL] time difference

[q u a d r a]

I have a query that returns
?column?
-
 6 days 01:56:14
(1 row)


How can I get it as total number of hours?
Instead of days and hours, I need hours only (all in all, so 24hours * 6 
days + 01:56:14)
Can you help me please? Thanks




---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

[SQL] German "umlaut insensitive" query

[=?ISO-8859-1?Q?Robert_Str=F6tgen?=]

I want to query words with German "umlauts" (special characters) with
and without normalization. I want to find "grün" (green) written
"gruen" as well.
Using "LIKE" with locale de_DE.iso88591 or .utf-8 does not help (Locale 
support should affect "LIKE",
http://www.postgresql.org/docs/7.3/static/charset.html#AEN21761).

Any Idea how to solve this? Define a special Operator? Has anyone
already done this before?
I am using PostgreSQL 7.3.2 on Linux.
TIA,
Robert Strötgen. :)
--

  Robert Strötgen
  mailto:[EMAIL PROTECTED]  http://www.stroetgen.de/

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
 subscribe-nomail command to [EMAIL PROTECTED] so that your
 message can get through to the mailing list cleanly

Re: [SQL] German "umlaut insensitive" query

[=?ISO-8859-1?Q?Robert_Str=F6tgen?=]

select replace( replace( replace( replace( 'Test ä ö ü ß', 'ä','ae'), 
'ö','oe' ), 'ü','ue'), 'ß','ss' );
Thanks a lot. A wrote this into a user defined function with lower() 
around the source string, and it works. :-)

CREATE OR REPLACE FUNCTION public.unumlaut(varchar)
  RETURNS varchar AS
'select replace( replace( replace( replace( lower($1), \'ä\',\'ae\'), 
\'ö\',\'oe\' ), \'ü\',\'ue\'), \'ß\',\'ss\' );'
  LANGUAGE 'sql' IMMUTABLE STRICT;

Best regards,
Robert. :)
--

  Robert Strötgen
  mailto:[EMAIL PROTECTED]  http://www.stroetgen.de/

---(end of broadcast)---
TIP 6: Have you searched our list archives?
  http://archives.postgresql.org

Re: [SQL] create unique index schema.index_name on table (column)?

[=?ISO-8859-1?Q?m=D8ntar3?=]

I'm working with a closed source application that reads an ASCII file 
and as it does it (via ODBC) creates tables and indexes, inserting as it 
goes. Like so:

CREATE TABLE bgsuser.CAXCTRLD ( CTRLS INTEGER, INTVL INTEGER);
CREATE UNIQUE INDEX bgsuser.PRIMARY_CAXCTRLD ON bgsuser.CAXCTRLD 
(CTRLS,INTVL);
INSERT ...
INSERT ...

The application is designed to work through ODBC and psqlODBC does a 
great job. My problem is the username (schema qualifier) on the create 
index statement. I've decided it's easiest to copy/paste/modify the 
create statements from the ODBC trace logs.. oh, well.

Michael Glaesemann wrote:
On Sep 12, 2004, at 5:42 AM, [EMAIL PROTECTED] wrote:
Is the syntax "schema_name.index_name" for create unique index wrong, 
unsupported or what? I know is doesn't work as postgres kicks me back 
a syntax error each time (version 7.3.2 & 7.4.5). -sigh-

Could you give a full example (including the error) of what you're 
doing? It's kind of hard to give a suggestion based on your brief 
description.

Michael

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [SQL] Storing properties in a logical way.

[=?iso-8859-15?Q?Pierre-Fr=E9d=E9ric_Caillaud?=]

But after looking closely at the list of a possible properties, i found
out that some of them depend on others. For example, if item is a
PDF document, it can have an index. But a document can also have an
index with links. Logically, a properties like 'index with links'
don't belong to the verification table - they look like a kind of
a composite field - 'index with links' is not a stand-alone property,
but it also implies that an item also has an 'index' property.
On the other hand, it is impossible to decouple 'index' from
'with links', because the second part won't have any meaning without
the first part.
You mean your properties would be better organized as a tree ?
Or is it even more complicated than that ?
If it's a tree, look at the ways of storing a tree in a table.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
  http://archives.postgresql.org