Renaming/Deleting DB Column

[Hannes]

Hei,

when renaming or deleting a DB Column in the Field Settings
I will get a error message when trying to add submissions again.

Code:

Unknown column 'fieldname' in 'field list'

If manually renaming/deleting in mysql it is fine again.
I use this feature quite a lot when sharing the database with other applications.

This is for 2.1.0-beta-20110730

Best regards,
Hannes

[Ben]

Hmm! Curious - I haven't encountered that.

I'll check it out. Thanks!

- Ben

[Hannes]

Hmm!, too... You did not change anything here in the last update?
I was just going to test whether there was a problem with my mysql privileges...
But now it's working even without having changed anything from my side.

If I can reproduce the problem again I will let you know...
But for now it is working again...

[Ben]

Curious! No, I don't think I made any fixes for this one, so do let me know if it crops up again!

- Ben

[Hannes]

Hi Ben,

I was able to catch this bug in action - it was a very tiny one... (-;
It does happen also in 2.1.0-beta-20110808 when you do both, delete a column and add a column, before pressing "update".

delete-update-add-update - works...
delete-add-update - does not... it does not delete from mysql.

Nice time.
Hannes.

[Ben]

Hi Hannes!

I just fixed this problem locally. It was introduced a little while ago in which field records were deleted in the Form Tools database, but the actual database table wasn't updated to remove the column. So if you try to create new fields with field names that already exist in the db, you'll see an error.

I'll include this fix in today's build. However, you'll need to manually delete those fields from your database if you want to reuse the same database column names.

- Ben

[One of the modules I would like to eventually get around to, is a "Spring Clean" module that checks the integrity of the database content - sort of like a data counterpart to the Database Integrity module. That would identify and fix problems like this. Just thought I'd mention it.]

[Hannes]

Hi Hannes!

I just fixed this problem locally. It was introduced a little while ago in which field records were deleted in the Form Tools database, but the actual database table wasn't updated to remove the column. So if you try to create new fields with field names that already exist in the db, you'll see an error.

I'll include this fix in today's build. However, you'll need to manually delete those fields from your database if you want to reuse the same database column names.

- Ben

[One of the modules I would like to eventually get around to, is a "Spring Clean" module that checks the integrity of the database content - sort of like a data counterpart to the Database Integrity module. That would identify and fix problems like this. Just thought I'd mention it.]

Ok. Great!
When I opened this thread, I thought it was a general bug in column management.
It did not cause any problem, later everything was running perfect until I finally got it again.
I was just happy to find out where the problem was i had in the beginning and that it was not only a problem on my side. (-;