On 01/05/13 19:21, Merlin Moncure wrote:
On Wed, May 1, 2013 at 11:34 AM, Andrew Hastie and...@ahastie.net wrote:
On 01/05/13 15:34, Merlin Moncure wrote:
On Wed, May 1, 2013 at 8:01 AM, Andrew Hastie and...@ahastie.net wrote:
On 30/04/13 20:46, Merlin Moncure wrote:
On Tue, Apr 30, 2013 at
Thank you Jasen/Karsten for your guidance.
Best Regards,
Dinesh
manojadinesh.blogspot.com
On Sat, Apr 20, 2013 at 3:43 PM, Jasen Betts ja...@xnet.co.nz wrote:
On 2013-04-15, dinesh kumar dineshkuma...@gmail.com wrote:
--047d7b675e70cee73c04da61865c
Content-Type: text/plain;
Hello Team,
I would like to know whether the following behavior is a BUG or an expected
behavior. If this is a duplicated case, then kindly ignore.
postgres=# SELECT version();
version
-
PostgreSQL 9.2.3,
This behavior is similar to strstr(3) ('needle in a haystack'
substring locating C function).
char *strstr(const char *haystack, const char *needle)
which returns haystack (that is main string) if needle (string to be
located) is empty.
Assuming position() tries to do something similar, it
dinesh kumar dineshkuma...@gmail.com writes:
postgres=# select position('' in 'PostgreSQL'); *// position(Substring as
an empty string) is returning 1.*
position
--
1
(1 row)
This is correct according to the SQL standard:
position expression determines the first
Hi Tom,
Thank you very much for the clarification.
Let me set an empty string validation, before passing it to position()
from API.
Thank you once again.
Regards,
Dinesh
manojadinesh.blogspot.com
On 2 May 2013 19:19, Tom Lane t...@sss.pgh.pa.us wrote:
dinesh kumar dineshkuma...@gmail.com
On 2013-05-01 10:17, Larry Rosenman wrote:
I have an app that we have a number of tables that all have FK
relationships with the account table.
We did a massive (2900+ account, probably multi-thousand rows) delete
from all the tables, and the
delete from the account table is taking a lot of
Larry Rosenman l...@lerctr.org writes:
Question: Do all these need to have a bare index just on the account_id
column, or is a multicolumn index with account_id first
sufficient for the check to be reasonably quick?
I would think that such an index would be sufficient, but you could
check for
On 2013-05-02 10:08, Tom Lane wrote:
Larry Rosenman l...@lerctr.org writes:
Question: Do all these need to have a bare index just on the
account_id
column, or is a multicolumn index with account_id first
sufficient for the check to be reasonably quick?
I would think that such an index would
This behavior is similar to strstr(3) ('needle in a haystack'
substring locating C function).
which is,
char *strstr(const char *haystack, const char *needle)
which returns haystack (that is main string) if needle (string to be
located) is empty.
Assuming position() tries to do something
Any idea?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Save-postgresql-node-to-catch-only-DML-except-delete-queries-tp5753603p5753863.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list
11 matches
Mail list logo