Incosistent/Incorrect Truncate behavior

Asked by Amit Saha on 2009-04-20

Please take a look at http://bugs.mysql.com/bug.php?id=43547 and comment on the behaviour of PBXT against the other engines.

Question information

Language:
English Edit question
Status:
Solved
For:
PBXT Edit question
Assignee:
No assignee Edit question
Solved by:
Amit Saha
Solved:
Last query:
Last reply:
Revision history for this message
Paul McCullagh (paul-mccullagh) said :
#1

Hi Amit,

I implemented this feature without looking at the manual. Probably a mistake. So I implemented in a way that I thought makes sense, namely that the engine actually remembers what value you set.

PBXT has to do this for other things like foreign key, so storing the AUTO_INCREMENT minimum value is not a problem.

So, I agree with you that this make more sense then the way other engines work, but it looks like I am going to have to change it anyway, in order to be compatible.

Revision history for this message
Amit Saha (amit-saha) said :
#2

Hello Paul,

Do you suggest, then to file it as a bug report in PBXT?

Thanks,
Amit

Revision history for this message
Paul McCullagh (paul-mccullagh) said :
#3

Yes, this must be considered a PBXT bug.

Revision history for this message
Amit Saha (amit-saha) said :
#4

Thanks! Bug filed.