[Date Prev][Date Next]
Re: back-sql mysql innodb
- To: email@example.com
- Subject: Re: back-sql mysql innodb
- From: Frederik Bosch <firstname.lastname@example.org>
- Date: Wed, 28 Jul 2010 14:22:04 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=jPDE2Xn1hRWsrMp03VfZx03yuITLW2ePNqb3YoTi/pQ=; b=E/UFBSpacj/x7OVPwCiuqjsKwthBCu1yCP1mPqyfPSYHKIjJhwjgbwotytVfLZLSdG lHK/5vJ3vN4J2/JN6t+KinrZv59L96huQ+EzIvIziZyte6+h9TleDCnYT50ek9j8rAyz Z9XRFMZ3N14LvPmApdt36Nzhcwa71o2OqISY0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=K22qvlN7y2l42sGBEpDUrcETofATpVPkdNjzaeK84KkY6JvqiPb6Bv+lE2ERTDngFa lRnZ4MEz3HsH+CTEGfHt6fkvd17Xjw3C59dKhirk5RXrf+hGd6Q3cnUJs5u3DoJE8Ro8 WZFVOLb601qgArXUIoZjdjGTKfB1kbODHNzpU=
- In-reply-to: <4C500752.email@example.com>
- References: <4C500752.firstname.lastname@example.org>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20100713 Thunderbird/3.0.6
Problem solved. I had to comment a line in sql_wrap.c:
* TimesTen : Turn off autocommit. We must explicitly
* commit any transactions.
SQLSetConnectOption( *dbhp, SQL_AUTOCOMMIT, SQL_AUTOCOMMIT_OFF );
This last line actually prevents slapd from updating resultsets (which
are committed) in InnoDB.
Perhaps autocommit should be enabled by default, but the user should be
able to disable it through a configuration option in slapd.conf. Should
I file a request or bug for this?
On 07/28/2010 12:32 PM, Frederik Bosch wrote:
Two weeks ago I also wrote to this mailinglist, but now my problem is
much more clear. I succesfully installed slapd and managed to start it
with back-sql. However, I have one problem. Once slapd has retrieved
childs from a certain entry, it is not able to refresh it. A slapd
restart is needed for that.
The problem is due to the MySQL engine used: InnoDB. I discovered that
when I converted my database to MyISAM, which had no problems at all.
Upgrading myodbc to version 5.1.6 (I as on 3.51 before) did not help.
Converting to MyISAM is not an option and was just for testing.
Restarting the server each 5 minutes looks like a ugly solution to me.
What could be wrong?