It was my understanding from Kai that the alter SQL command was not supported because it would compromise the performance tuning of Texis database tables. Would adding support for ALTER, have a negative impact on Texis performance?
For the current scheme ALTER would need to go through the same steps outlined above, and the main benefit would be the reduced amount of SQL that would need to be entered. We are looking at an improved format for Texis tables, which would allow an ALTER to occur rapidly with no impact on performance.
I've tried using the "INSERT INTO NewTable..." method for adding a new column. TEXIS seems to have a problem with the BLOB field I have in the original table. It creates the new table but only half the field for the first record get moved over. The last field that's successfuly copied is the field prior to the BLOB. I tried creating the table without the BLOB and all the data moves over without any problems. Do you have any idea why this is happening?