RE: [otrs] Using apostrophes in the subject causing problems

Here's the kicker:
Just for fun, I took the same otrs installation, created a mysql database, changed a few config files to point otrs to the mysql database (instead of postgres) and magically all my problems I've been emailing this thread about disappeared!
The apostrophe issue can't be duplicated. The case sensitive search issue is fixed also now.
I made a few more changes and we have now switched to using mysql permanently.
Thanks for everyone's help here.
Carl Sheline
School of Dentistry
Loma Linda University
-----Original Message-----
From: otrs-bounces@otrs.org on behalf of Bryan Fullerton
Sent: Tue 7/5/2005 2:19 PM
To: User questions and discussions about OTRS.org
Subject: Re: [otrs] Using apostrophes in the subject causing problems
On 6/30/05, Jeremy Blain
This sounds like an sql escaping issue, where placeholders or proper quoting should be used for all the data, but isn't correct. (this is potentially a security issue too)
I've filed a bug report about it http://bugs.otrs.org/show_bug.cgi?id=809
This is the same as a bug I filed in May. http://bugs.otrs.org/show_bug.cgi?id=732 It also seems to be the same as this bug. http://bugs.otrs.org/show_bug.cgi?id=788 For what it's worth I haven't seen this bug recently, but I also haven't seen any email recently with apostrophes in the subject. Bryan _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? =http://www.otrs.de/

On 7/5/05, Sheline, Carl (LLU)
I made a few more changes and we have now switched to using mysql permanently.
I'm tempted to do the same, but I'm concerned that moving three years of tickets will be non-trivial. Will any development work be done to resolve outstanding PostgreSQL issues, or is it no longer a supported database for OTRS? Bryan

On Wed, 2005-07-06 at 14:02 -0400, Bryan Fullerton wrote:
On 7/5/05, Sheline, Carl (LLU)
wrote: I made a few more changes and we have now switched to using mysql permanently.
I'm tempted to do the same, but I'm concerned that moving three years of tickets will be non-trivial.
Will any development work be done to resolve outstanding PostgreSQL issues, or is it no longer a supported database for OTRS?
Bryan I sure hope postgres will continue to be supported.
Mysql's ability to flip the status of their license at any time does not make for a warm fuzzy feeling. Regards, Ted

Hi Brian and all, On Wed, Jul 06, 2005 at 02:02:02PM -0400, Bryan Fullerton wrote:
On 7/5/05, Sheline, Carl (LLU)
wrote: I made a few more changes and we have now switched to using mysql permanently.
I'm tempted to do the same, but I'm concerned that moving three years of tickets will be non-trivial.
Will any development work be done to resolve outstanding PostgreSQL issues, or is it no longer a supported database for OTRS?
Of course postgresql will be supported in future. But because we use MySQL for most installations, we don't recognize postgresql errors as fast as MySQL problems. For that reason please make bug reports on http://bugs.otrs.org if there are problems with postgresql. We'll test and try to fix them.
Bryan
Best regards, Christian -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!

On 7/8/05, Christian Schoepplein
Of course postgresql will be supported in future. But because we use MySQL for most installations, we don't recognize postgresql errors as fast as MySQL problems. For that reason please make bug reports on
There are bug reports in the system. http://bugs.otrs.org/show_bug.cgi?id=732 http://bugs.otrs.org/show_bug.cgi?id=788 I've updated mine to reflect that it's still an issue with beta4 and other updates (perl, postgresql, etc). Bryan

Hi @ll, On Fri, Jul 08, 2005 at 10:24:27AM -0400, Bryan Fullerton wrote:
On 7/8/05, Christian Schoepplein
wrote: Of course postgresql will be supported in future. But because we use MySQL for most installations, we don't recognize postgresql errors as fast as MySQL problems. For that reason please make bug reports on
There are bug reports in the system.
http://bugs.otrs.org/show_bug.cgi?id=732 http://bugs.otrs.org/show_bug.cgi?id=788
I've updated mine to reflect that it's still an issue with beta4 and other updates (perl, postgresql, etc).
I tryed it now on my system with an actual OTRS from the cvs head, postgresql 8 on a debian system. I wasn't able to reproduce the problems with abostrophes in the subject or other fields. I think that a recent version of DBD::Pg will solve all these problems. I use 1.42-2 (libdbd-pg-perl 1.42-2 on debian unstable). It would be nice, if someone else could test this with a newer version of DBD::Pg too and post if it was successful or not.
Bryan
Best regards and thanks for the help, Christian -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!

Christian Schoepplein wrote:
Hi @ll,
On Fri, Jul 08, 2005 at 10:24:27AM -0400, Bryan Fullerton wrote:
On 7/8/05, Christian Schoepplein
wrote: Of course postgresql will be supported in future. But because we use MySQL for most installations, we don't recognize postgresql errors as fast as MySQL problems. For that reason please make bug reports on
There are bug reports in the system.
http://bugs.otrs.org/show_bug.cgi?id=732 http://bugs.otrs.org/show_bug.cgi?id=788
I've updated mine to reflect that it's still an issue with beta4 and other updates (perl, postgresql, etc).
I tryed it now on my system with an actual OTRS from the cvs head, postgresql 8 on a debian system. I wasn't able to reproduce the problems with abostrophes in the subject or other fields.
I think that a recent version of DBD::Pg will solve all these problems. I use 1.42-2 (libdbd-pg-perl 1.42-2 on debian unstable). It would be nice, if someone else could test this with a newer version of DBD::Pg too and post if it was successful or not.
I'll give it a try as soon as I have some time, I have a couple debian systems at home.

On 7/12/05, Christian Schoepplein
I tryed it now on my system with an actual OTRS from the cvs head, postgresql 8 on a debian system. I wasn't able to reproduce the problems with abostrophes in the subject or other fields.
I think that a recent version of DBD::Pg will solve all these problems. I use 1.42-2 (libdbd-pg-perl 1.42-2 on debian unstable). It would be nice, if someone else could test this with a newer version of DBD::Pg too and post if it was successful or not.
I'm using a more recent version of DBD::Pg than you are. I've updated the bug report with the correct version. From my FreeBSD system: % pkg_info -xI Pg p5-DBD-Pg-1.43 Provides access to PostgreSQL databases through the DBI However, I'm using PostgreSQL v7.4.8, not v8. I'll have to investigate what impacts there'd be to upgrading to v8 for testing here - OTRS is not the only application using that PostgreSQL instance. Do you have any way to test with v7.x? Thanks, Bryan

On 7/12/05, Christian Schoepplein
I tryed it now on my system with an actual OTRS from the cvs head, postgresql 8 on a debian system. I wasn't able to reproduce the problems with abostrophes in the subject or other fields.
Christian later noted in the bug system (bug 781) that he was able to reproduce this issue with apostophes and other special characters in the Subject field, and that it happened regardless of the database back-end. I have confirmed that this issue still exists with 2.0.1. I'll update the bug once bugs.otrs.org returns. Thanks, Bryan
participants (5)
-
Bryan Fullerton
-
Christian Schoepplein
-
Jeremy Blain
-
Sheline, Carl (LLU)
-
Ted Kaczmarek