![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
![]() |
Wed, May 17 2006 7:35 AM | Permanent Link |
Dave M | I made the mistake of doing this:
START TRANSACTION WITH sometable; ALTER sometable ADD COLUMN if not exists "somecolumn" date; COMMIT FLUSH This causes a 11279 access violation in a query c/s 4.23b and in dbsys (both c/s and local). This error shows up in the server log. Since transactions are incompatible with alter, I would remove the transaction in the future. Tim, is this a minor incident report, old news, what? Dave M. |
Wed, May 17 2006 4:14 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Dave,
<< I made the mistake of doing this: START TRANSACTION WITH sometable; ALTER sometable ADD COLUMN if not exists "somecolumn" date; COMMIT FLUSH This causes a 11279 access violation in a query c/s 4.23b and in dbsys (both c/s and local). This error shows up in the server log. >> It's a bug with the restricted transactions and ALTER TABLE. The ALTER TABLE should just cause the transaction to commit automatically: http://www.elevatesoft.com/dbisam4d5_transactions.htm "Incompatible Operations" -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Monday, July 7, 2025 at 06:35 PM | Privacy Policy![]() © 2025 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |