[SQL] Like seems to fail !

[Yves Martin]

Hello,

I have a strange problem with 'like' behaviour 
when I upgrade from 6.5 to 7.0

Here is my table :

create table persistent_config (
key varchar primary key,
typevarchar(12),
value   varchar not null
)

and its content :

base=# select * from persistent_config;
key | type |value 
+--+--
 /test/info |  | avalue
 /try/info  |  | avalue
 /test/key  |  | changedvalue
(3 rows)

And I try this 'like' command in psql :

base=# select * from persistent_config where key like '/test%';
key | type |value 
+--+--
 /test/info |  | avalue
 /test/key  |  | changedvalue
(2 rows)

 Result is ok !

   By now, this other one :

base=# select * from persistent_config where key like '/%';
 key | type | value 
-+--+---
(0 rows)

 There is really something wrong !  All current content should have been
 returned. Is '/' caracter a new 'escape' caracter since version 6.5
 In fact, my query was working well on postgresql 6.5 and since I upgraded
 to 7.0, this simple command failed.
     Is it a bug, or I missed something ?

  Regards

-- 
Yves Martin
yma, Lausanne

[SQL] Like seems to fail !

[Yves Martin]

Hello,

I have a strange problem with 'like' behaviour 
when I upgrade from 6.5 to 7.0

Here is my table :

create table persistent_config (
key varchar primary key,
typevarchar(12),
value   varchar not null
)

and its content :

base=# select * from persistent_config;
key | type |value 
+--+--
 /test/info |  | avalue
 /try/info  |  | avalue
 /test/key  |  | changedvalue
(3 rows)

And I try this 'like' command in psql :

base=# select * from persistent_config where key like '/test%';
key | type |value 
+--+--
 /test/info |  | avalue
 /test/key  |  | changedvalue
(2 rows)

 Result is ok !

   By now, this other one :

base=# select * from persistent_config where key like '/%';
 key | type | value 
-+--+---
(0 rows)

 There is really something wrong !  All current content should have been
 returned. Is '/' caracter a new 'escape' caracter since version 6.5
 In fact, my query was working well on postgresql 6.5 and since I upgraded
 to 7.0, this simple command failed.
     Is it a bug, or I missed something ?

  Regards,

-- 
Yves Martin
yma, Lausanne

[SQL] Statement too long

[Yves Martin]

Hello,

   I have some problem with too long statement.
  In 'psql', the error returned for my insert statement is
ERROR: Tuple is too big: size 10436

  In fact, I use JDBC driver to insert a long long string into a 'text'
  field. The exception is

The SQL Statement is too long - INSERT INTO TRIGGERQUEUE   (DUETIME,
TYPE, EVENT, ACTION) VALUES( 974992122555, 'CONTAINER', 
.(long really long)...

  So is it possible to re-build postmaster to avoid this limitation for
  too long statement or is there another way in JDBC ?

  Another problem is that with jdbc 6.5 and 7.0 the example of using largeobject
  in postgreSQL development corner site does not work. It returns an exception:
  setBinaryStream does not support an input as an InputStream.
  So how to make this exemple work ?

 Regards
  
-- 
Yves Martin
yma, Lausanne