On 7/12/05, Christian Schoepplein [EMAIL PROTECTED] wrote:
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
Hi @ll,
On Fri, Jul 08, 2005 at 10:24:27AM -0400, Bryan Fullerton wrote:
On 7/8/05, Christian Schoepplein [EMAIL PROTECTED] 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.
Christian Schoepplein wrote:
Hi @ll,
On Fri, Jul 08, 2005 at 10:24:27AM -0400, Bryan Fullerton wrote:
On 7/8/05, Christian Schoepplein [EMAIL PROTECTED] wrote:
Of course postgresql will be supported in future. But because we use
MySQL for most installations, we don't recognize
On 7/12/05, Christian Schoepplein [EMAIL PROTECTED] wrote:
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
Hi Brian and all,
On Wed, Jul 06, 2005 at 02:02:02PM -0400, Bryan Fullerton wrote:
On 7/5/05, Sheline, Carl (LLU) [EMAIL PROTECTED] 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
On 7/8/05, Christian Schoepplein [EMAIL PROTECTED] 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
On 7/5/05, Sheline, Carl (LLU) [EMAIL PROTECTED] 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
On Wed, 2005-07-06 at 14:02 -0400, Bryan Fullerton wrote:
On 7/5/05, Sheline, Carl (LLU) [EMAIL PROTECTED] 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
On 6/30/05, Jeremy Blain [EMAIL PROTECTED] wrote:
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
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 [EMAIL PROTECTED] wrote:
This sounds like an sql escaping issue, where placeholders or proper
quoting
should
questions and discussions about OTRS.org
Subject: Re: [otrs] Using apostrophes in the subject causing problems
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
I'm using OTRS 1.3.2
When I create a phone ticket and type someone's computer needs blah
blah in the subject and then finish out filling the rest of the ticket
and then click on create I get this error message:
Error: called with 2 bind variables when 0 are needed, SQL: 'INSERT INTO
article
Of Jeremy Blain
Sent: Thursday, June 30, 2005 12:18 PM
To: User questions and discussions about OTRS.org
Subject: Re: [otrs] Using apostrophes in the subject causing problems
This sounds like an sql escaping issue, where placeholders or proper quoting
should be used for all the data, but isn't correct
13 matches
Mail list logo
