Yes, you are right. The error was, that i saved long text as part of a prepared statement by using the ascii-stream. Yesterday i recognized (at least), that i can save without any problem long text as part of a normal insert-string. And then the queries are working like they should.
Sometimes even the simple things can be that difficult :-) Best, Michael > -----Ursprüngliche Nachricht----- > Von: Haller Christoph [mailto:[EMAIL PROTECTED]] > Gesendet: Freitag, 28. September 2001 16:11 > An: Michael Remme > Cc: [EMAIL PROTECTED] > Betreff: Re: [SQL] TEXT in select > > > I've tried (column indexdef is of type text) > select indexdef from pg_indexes where indexdef like '%pg_proc%' ; > select indexdef from pg_indexes where position('pg_proc' in > indexdef) > 0 ; > select upper(indexdef) from pg_indexes where position('pg_proc' > in indexdef) > 0 ; > and all three worked as intended. > Sorry, but I can't see any reason why it doesn't work on your machine. > Regards, Christoph > > > Hi, > > > > does anybody know a way, how to implement the content of a field of type > > TEXT > > into a query? > > > > if i am trying: > > select * from testtable WHERE testTEXT LIKE '%testString%' > > > > i am getting always an empty selection, although there is a > record existing. > > The same with > > > > select * from testtable WHERE position ('testString' in > testTEXT) > > > 0; > > > > Additional, is there a way to use the UPPER()-function to the > content of the > > TEXT-field? > > > > Thanks in advance, > > Michael > > Virengeprüft vom G DATA AntiVirenKit ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
