can't rename field names in existing table

[Former user]

Originally reported on Google Code with ID 101 ``` What steps will reproduce the problem? 1. create db, table with fields like (id, info, parend_id) 2. try to rename mixed-up filed name 'parend_id' to 'parent_id' in table Structure page 3. script gives you no error, but the field name is steel old (wasn't change)

What is the expected output? What do you see instead? I expected to see an old column named with a new name. But no changes were done.

What version of the product are you using? On what operating system? SQLite version: 3.7.7 SQLite extension : PDO PHP version: 5.3.6-13ubuntu3.6

Please provide any additional information below.

since there is no easy way to rename fields in sqlite natively (alter table in sqlite doesn't change field names), you can see some ways to workaround it here:

http://stackoverflow.com/questions/805363/how-do-i-rename-a-column-in-a-sqlite-database-table

```

Reported by `[e-mail]` on 2012-04-28 07:38:40

[Christopher Kramer]

``` Thanks for reporting this and especially for the link. But I consider this a duplicate of issue #12. We will really need to look at this, but I guess it's not simple. If you look at issue #12, I was affected by this issue myself (before joining the phpLiteAdmin-team). ```

Reported by `crazy4chrissi` on 2012-06-02 20:21:38 - Status changed: `Duplicate` - Merged into: #12

[Former user]

``` Hi. I congratulate you to become a new dev team member and wish you prolific work )). You can probably merge it, but my bug was about names in a tables and your bug was about changing structure of a tables. Probably it causes the same errors in mechanism logic, but all the trobles should be listed in a bug if you want to merge it, because: -Your and mine problems may be caused by different errors, we don't know it yet, right? -Everithing that wasn't mentioned is going to forget. golden rule. So if this bugtracking system has an ability to bound task together 12 and 102 should be bounded. If not, all the problems from all the relative bugs should be literally listed in the merged superbug ))

May be i am a little bit paranoid about this, that's because i am working in a bug-testing and support team )).

Good luck.

03.06.2012 02:21, [e-mail] написал: ```

Reported by `[e-mail]` on 2012-06-04 05:51:19

[Christopher Kramer]

``` Hi, thanks for your answer.

Just to get this right: Your bug happens when changing the name of a column, right? So that's basically changing structure ("schema") as well. I agree that issue #12 was originally about deleting a column which is not exactly the same thing, but in issue

1. 12 it was already discussed that changing column names causes the same problem. And I doubt this has two completely different reasons.

About "everything is going to forget", you are right in a sense. I do not really like the way google code merges duplicate bugs. In fact it should push more data from the duplicate to the original bug. But already, your problem (changing column name) has been mentioned in issue #12. And there is the link in issue #12 to this one now, so it is not really lost.

It's somehow a matter of taste (granularity of bugs), but I somehow felt these bugs really belong together. Problem with duplicates like this is that with multiple developers or committers working on a project, duplicate fixes might be developed (for an example, I fixed issue #75, although somebody has already fixed it in issue #72). And that's a waste of resources. ```

Reported by `crazy4chrissi` on 2012-06-04 17:17:25

[Former user]

``` yes, you mentioned it in comment #17. but who reads comments when It's going to close the bug as soon as it possible ? )) so it goes to trash can again. edit the report message in top of the thread like this:

s/edit the table and remove one of the columns/edit the table and remove or rename one of the columns/

and i'll go happy with this ))

finally developers shouldn't ask people to make decisions, but they should make their job honestly and gather the info. what if i don't care? you merge bugs, half of info will be lost, nobody cares -> software functionality lacks. just make it organized in the best way as it possible, and it'll go in a right way on it's own. and you know what is the best way ;) ```

Reported by `[e-mail]` on 2012-06-04 17:40:34

[Christopher Kramer]

``` I renamed issue #12 including the problem of this issue. I also included changing types.

Okay, now let's close this discussion, so we don't spend more time on it than fixing the issue would have needed.

Btw, I hope people read comments when fixing issues. At least I do (if it's not 500 of them)... ```

Reported by `crazy4chrissi` on 2012-06-04 17:50:35