[SQL] Finding broken regex'es

2007-10-02 Thread Enrico Weigelt
the db ? thx -- ----- Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.

Re: [SQL] Database synchronization

2007-08-08 Thread Enrico Weigelt
primary database. So time critical things are separated to own servers. It works quite fine :) cu -- --------- Enrico Weigelt== metux IT service - http://www.metux.de/ -

[SQL] Performance on writable views

2007-08-08 Thread Enrico Weigelt
ive me some details about that issue ? cu -- --------- Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Tas

[SQL] Implementing an regex filter

2007-08-08 Thread Enrico Weigelt
the second query would be much faster (about 2mins vs. 18mins). But I really wonder, why is processing one huge regex so dramatically slow ? BTW: in some tables I'm using the username instead (or parallel to) the numerical id to skip joins against the user table. But I'm not sure if

Re: [SQL] Converting from MS Access field aliases

2007-08-08 Thread Enrico Weigelt
n views, but is this always very performant ? cu -- --------- Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce:

[SQL] Mutex via database

2005-05-04 Thread Enrico Weigelt
ction dies ? thx -- ----- Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL

Re: [SQL] pgtop, display PostgreSQL processes in `top' style

2005-05-01 Thread Enrico Weigelt
it - its just some keystrokes away for me) cu -- --------- Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] ---

Re: [SQL] trigger/rule question

2005-05-01 Thread Enrico Weigelt
te (AFAIK), so we cannot intercept here. the only chance seems to leave out "INSTEAD" and live with duplicate data. Did I miss anyting ? cu -- --------- Enrico Weigelt== metux IT service phone: +49 36207 519931

Re: [SQL] trigger/rule question

2005-05-01 Thread Enrico Weigelt
pdates within the application, but I wanna get away from that. It probably would be interesting, if a normal application couldn't touch the mtime at all. cu -- --------- Enrico Weigelt== metux IT service phone:

[SQL] trigger/rule question

2005-04-27 Thread Enrico Weigelt
yet. Any ideas ? thx -- --------- Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] - Real

[SQL] RULE for mtime recording

2005-04-21 Thread Enrico Weigelt
SET bar = 'xyz' WHERE ... the mtime should be set to the current time, but on UPDATE foo SET bar = '123', mtime = '2001-09-11' WHERE ... we shall have 9/11 as mtime. Is this possible with rules ? thx -- ----------

[SQL] checking pgsql functions

2005-04-20 Thread Enrico Weigelt
gle crashing trigger may cost a lot of money). So I'd like to checkin only syntactically correct (also with correct references). Is it possible somehow ? cu -- --------- Enrico Weigelt== metux IT service phone: +49

Re: [SQL] Table PARTITION

2005-04-07 Thread Enrico Weigelt
with partitions, with a little bit more coding work, but then with better control and filtering out unneeded stuff. cu -- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.

[SQL] asynchrous triggers

2005-03-31 Thread Enrico Weigelt
hi folks, is it possible somehow to make (AFTER) triggers run in their own process/thread, so the calling session can return immediately and the trigger runs in background ? thx -- - Enrico Weigelt== metux IT service

[SQL] (non)zero function

2005-03-27 Thread Enrico Weigelt
-- - Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] cellphone: +49 174 7066481

[SQL] detaching triggers

2005-03-27 Thread Enrico Weigelt
r idea out these ? thx -- ----- Enrico Weigelt== metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: [EMAIL PROTECTED] cellphone: +49 1