Hi,
I am trying to implement an automated log-message system for my
application. For example, if a new user is inserted to my table "auth",
I want to create a log message like: "user [name] added to system". Is
it possible to add this message with triggers or rules?! If so, can
anyone give some e
On Fri, Jan 12, 2001 at 07:59:26 +0100, Joern Muehlencord wrote:
> I am trying to implement an automated log-message system for my
> application. For example, if a new user is inserted to my table "auth",
> I want to create a log message like: "user [name] added to system". Is
> it possible to add
Hi Tom and Stephan,
Thanks for your help guys.
I'm using varchar constraint definitions now that are "CHECK ((foobar
ISNULL) OR (length(foobar) < 17))" The short-circuiting of OR's in
7.0.3 allow this to work without error, thereby avoiding the "Bad (null)
varchar() external representation" err
Justin Clift <[EMAIL PROTECTED]> writes:
> BTW - How do things normally get added to the FAQ?
It's not a FAQ until it's been asked, um, frequently. But you can
try to talk Bruce Momjian into adding it, if you like.
regards, tom lane
Hi Tom,
I think you are right. It does seem to barf on NULLS and
length(varchar), regardless.
Thanks for your assistance.
BTW - How do things normally get added to the FAQ? I would like to add
something about length(varchar) and NULLS not working in PostgreSQL
7.0.x
Regards and best wishes,
What locale and encoding are you using?
Evidently the LIKE index optimization is failing, but I would
not have guessed that a string like 1:0: would cause a problem,
especially not if all the entries in the column contain just
digits and colons.
You can find plenty of material about LIKE+index p
Justin Clift <[EMAIL PROTECTED]> writes:
> I haven't seen a mention of a maximum number of constraints of similar
> applying to a table. If so, then could someone please point me to it...
There is no such limit that I know of.
> Yet if I remove BOTH the "staff_details_phone_three" &
> "staff_de
Justin Clift <[EMAIL PROTECTED]> writes:
> "Bad (null) varchar() external representation"
This is a known stupidity in 7.0.* and before: length(varchar) doesn't
like NULLs:
play=> select length(null::varchar);
ERROR: Bad (null) varchar() external representation
It's fixed for 7.1. If it's rea
Everytime I have usually start the server manually
then runnig the deamons.But sometime (no many times) in 7.0.2 after killing the
server with its pid ,The server process doesn't get reinitialized
Has anybody faced this
problem?.. What other processes might would be still be running in b
Hi,
I use:
agro=# select version();
version
---
PostgreSQL 7.0.3 on i686-pc-linux-gnu, compiled by gcc 2.95.3
compiled with "--enable-locales --enable-encoding --with-tcl" options on
Mandrake LINUX 7.2 with
On Thu, 11 Jan 2001, Markus Wagner wrote:
> first of all, I looked at the mailing list list at th pg web site and I
> did not find a list named "pgsql-interfaces".
Hmmm. I see it at
http://www.postgresql.org/users-lounge/index.html
Perhaps you looked elsewhere, or you saw an old mirror? (In
Hi Joel,
first of all, I looked at the mailing list list at th pg web site and I
did not find a list named "pgsql-interfaces".
In pg_hba.conf I added one line at the bottom with the IP of the client:
host all 134.93.64.47 255.255.255.255 trust
In Access, after installing the
12 matches
Mail list logo
