328

I would need to rename a few columns in some tables in a SQLite database. I know that a similar question has been asked on stackoverflow previously, but it was for SQL in general, and the case of SQLite was not mentioned.

From the SQLite documentation for ALTER TABLE, I gather that it's not possible to do such a thing "easily" (i.e. a single ALTER TABLE statement).

I was wondering someone knew of a generic SQL way of doing such a thing with SQLite.

Community
  • 1
  • 1
joce
  • 9,624
  • 19
  • 56
  • 74

16 Answers16

482

Note that as of version 3.25.0 released September 2018 you can now use ALTER TABLE to rename a column.

Example to rename Really Bad : Column Name to BetterColumnName:

ALTER TABLE your_table
RENAME COLUMN "Really Bad : Column Name" TO BetterColumnName

According to keywords the use of "double-quotes" is the standard way

Original "create new and drop old table" answer below.


Say you have a table and need to rename "colb" to "col_b":

First create the new table with a temporary name, based on the old table definition but with the updated column name:

CREATE TABLE tmp_table_name (
  col_a INT
, col_b INT
);

Then copy the contents across from the original table.

INSERT INTO tmp_table_name(col_a, col_b)
SELECT col_a, colb
FROM orig_table_name;

Drop the old table.

DROP TABLE orig_table_name;

Last you rename the temporary table table to the original:

ALTER TABLE tmp_table_name RENAME TO orig_table_name;

Don't forget to re-create indexes, triggers, etc. The documentation gives a fuller picture of the gotchas and caveats.

Wrapping all this in a BEGIN TRANSACTION; and COMMIT; is also probably a good idea.

surfmuggle
  • 5,527
  • 7
  • 48
  • 77
Evan
  • 18,183
  • 8
  • 41
  • 48
  • 56
    And don't forget your indices. – Tom Mayfield Aug 17 '09 at 22:25
  • 11
    Very importantly the example code above is missing a transaction. You should wrap the whole thing in a BEGIN/END (or ROLLBACK) to ensure that the renaming either completes successfully or not at all. – Roger Binns May 15 '11 at 22:50
  • How should one deal with in terms of indicies? – joshim5 Jul 31 '11 at 20:24
  • After doing the insert, re-create your indices exactly the same way you did when you first created the table (adding new ones if relevant). – Evan Aug 01 '11 at 00:15
  • 6
    Anyone wishing to do this in android can implement transactions using [SQLiteDatabase.beginTransaction()](http://developer.android.com/reference/android/database/sqlite/SQLiteDatabase.html#beginTransaction%28%29) – bmaupin Jan 23 '12 at 20:25
  • Using `BEGIN TRANSACTION;` and `COMMIT;` didn't worked for me. Neither in SQLite Administrator nor in sqliteman. Removing both and my query was successful. – testing Feb 23 '12 at 13:56
  • @ThomasG.Mayfield what do you mean "don't forget your indices."? The answer appears well received and accurate, but your comment comes recommended and lead me to begin rebuilding my database from scratch tonight. – John Jun 28 '12 at 22:38
  • You just need to remember to re-apply all your indices to the new table. – Tom Mayfield Jun 29 '12 at 16:13
  • 2
    @ThomasG.Mayfield I'm confused as well about the indices comment. Aren't indices copied verbatim just like all of the other columns which are not renamed? – Jeff Axelrod Sep 05 '12 at 18:00
  • 9
    There's nothing in the code in the answer that copies indices. Creating an empty table and putting data into it only copies structure and data. If you want metadata (indices, foreign keys, constraints, etc.), then you also have to issue statements to create them on the replaced table. – Tom Mayfield Sep 05 '12 at 18:04
  • 19
    SQLite's `.schema` command is handy for showing the `CREATE TABLE` statement that makes the existing table. You can take its output, modify as needed, and execute it to create the new table. This command also shows the necessary `CREATE INDEX` commands to create the indices, which should cover Thomas's concerns. Of course, be sure to run this command before altering anything. – Mike DeSimone Mar 20 '13 at 17:57
  • 1
    This is exactly what DB Browser for SQLite (http://sourceforge.net/projects/sqlitebrowser/) does as well. You can know because it prints the SQL commands it executes for the edits you do through its GUI. –  Oct 31 '14 at 08:34
  • Isn't it better to load all data into memory, drop the old table, re-create it with the new definition, and put all data back to it (all inside a transaction) ? – android developer Apr 09 '15 at 07:43
  • @MikeDeSimone If I recreate the new table with an index on any columns for which the previous (now temp) table had, will the new table's indexes be built as I run the `INSERT INTO` commands to migrate the old data? – theblang Apr 26 '15 at 17:17
  • 1
    @mattblang I'd expect them to be, just like any other case where you're inserting into a table with indexes. – Mike DeSimone Apr 26 '15 at 17:46
  • What about `VACUUM;` after dropping the old table? – PeterCo Mar 25 '18 at 15:10
  • Renaming the old table is not advised. The official SQLite documentation here (https://www.sqlite.org/lang_altertable.html#otheralter) states: "[...] the initial rename of the table to a temporary name might corrupt references to that table in triggers, views, and foreign key constraints. The safe procedure on the left constructs the revised table definition using a new temporary name, then renames the table into its final name, which does not break links." – mliakos Nov 17 '21 at 12:26
107

This was just fixed with 2018-09-15 (3.25.0)

Enhancements the ALTER TABLE command:

  • Add support for renaming columns within a table using ALTER TABLE table RENAME COLUMN oldname TO newname.
  • Fix table rename feature so that it also updates references to the renamed table in triggers and views.

You can find the new syntax documented under ALTER TABLE

The RENAME COLUMN TO syntax changes the column-name of table table-name into new-column-name. The column name is changed both within the table definition itself and also within all indexes, triggers, and views that reference the column. If the column name change would result in a semantic ambiguity in a trigger or view, then the RENAME COLUMN fails with an error and no changes are applied.

enter image description here Image source: https://www.sqlite.org/images/syntax/alter-table-stmt.gif

Example:

CREATE TABLE tab AS SELECT 1 AS c;

SELECT * FROM tab;

ALTER TABLE tab RENAME COLUMN c to c_new;

SELECT * FROM tab;

db-fiddle.com demo


Android Support

As of writing, Android's API 27 is using SQLite package version 3.19.

Based on the current version that Android is using and that this update is coming in version 3.25.0 of SQLite, I would say you have bit of a wait (approximately API 33) before support for this is added to Android.

And, even then, if you need to support any versions older than the API 33, you will not be able to use this.

Lukasz Szozda
  • 162,964
  • 23
  • 234
  • 275
  • 9
    I'm implementing for an Android migration and unfortunately IntelliJ is showing a warning that it is not a valid SQL command. `database.execSQL("ALTER TABLE content RENAME COLUMN archiveCount TO dismissCount")`. **COLUM** is higlighted in red and it says *TO expected, got 'COLUMN'*. Unfortunately Android is still on SQLite version **3.19** which is why this does not work for me. – AdamHurwitz Oct 07 '18 at 03:51
  • I have trided the latest System.Data.SQLite (1.0.109.2) NuGet package in a test .NET (ver 4.7.2) console application , but without any success - got SQL logic error near "COLUMN": syntax error. Isn't that version 3.25.0 version part of the nuget package yet? – rychlmoj Oct 15 '18 at 07:13
  • 1
    edited: I have found on https://system.data.sqlite.org/index.html/doc/trunk/www/faq.wiki#q1 ,that the 1.0.109.x) is actually using SQLite 3.24 and the System.Data.SQLite using SQLite 3.25 is cheduled to be relased this month. – rychlmoj Oct 15 '18 at 07:43
  • 1
    FYI, unfortunately this has yet to be implemented by [Android's SQLite library](https://developer.android.com/reference/android/database/sqlite/package-summary). Hopefully they will update soon. – AdamHurwitz Dec 09 '18 at 21:02
  • 3
    I added a section for Android Support to prevent others from getting their hopes up. Based on Android 27's current usage of SQLite 3.19, we will have to wait until roughly API 33 before this feature gets added to Android, and even then it'll only be supported on the latest versions. Sigh. – Joshua Pinter Dec 15 '18 at 17:48
  • 1
    @JoshuaPinter Thanks for extending my answer. – Lukasz Szozda Dec 15 '18 at 17:55
  • 1
    Anyway I can rename column name with query at the moment? I also need this in my Migration like @AdamHurwitz – Rafael Dec 17 '18 at 11:57
  • Is it just me or is that example in the answer completely off? Isn't that renaming a table rather than a column? – confetti Mar 21 '20 at 21:40
  • @confetti Thank you very much. Yes, you are right and I just adjusted the example :) – Lukasz Szozda Mar 21 '20 at 21:54
62

Digging around, I found this multiplatform (Linux | Mac | Windows) graphical tool called DB Browser for SQLite that actually allows one to rename columns in a very user friendly way!

Edit | Modify Table | Select Table | Edit Field. Click click! Voila!

However, if someone want to share a programmatic way of doing this, I'd be happy to know!

joce
  • 9,624
  • 19
  • 56
  • 74
  • 1
    There is also a [Firefox add-on that does the same thing](https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/), Right click the column you want to rename and select "Edit Column". – Jacob Hacker May 31 '14 at 04:30
  • 1
    Even in openSUSE, it is available as a package: http://software.opensuse.org/package/sqlitebrowser –  Oct 31 '14 at 08:28
  • It's weird it has so many votes. We're talking about programming here (code). Why did you even post this answer here? – user25 Feb 24 '19 at 15:48
  • 3
    There's no mention of how to do this with code in my question. I just wanted to know how to rename a column in an SQLite DB. – joce Feb 25 '19 at 18:42
  • @joce I love you!!! (like a brother) got me in changed the field, voila. I had exported an MS Access table to SQLite and one of the field had a digit in front: 3YearLetterSent. Visual Studio made the class from the table but choked on the "3" digit at the front of the field name. I've know this, just wasn't watching. – JustJohn Mar 27 '19 at 20:00
  • On my Linux/Ubuntu I used `sudo apt install sqlitebrowser`. After changes make sure you quit the program and select update changes. – WinEunuuchs2Unix Mar 02 '21 at 16:47
56

While it is true that there is no ALTER COLUMN, if you only want to rename the column, drop the NOT NULL constraint, or change the data type, you can use the following set of commands:

Note: These commands have the potential to corrupt your database, so make sure you have a backup

PRAGMA writable_schema = 1;
UPDATE SQLITE_MASTER SET SQL = 'CREATE TABLE BOOKS ( title TEXT NOT NULL, publication_date TEXT)' WHERE NAME = 'BOOKS';
PRAGMA writable_schema = 0;

You will need to either close and reopen your connection or vacuum the database to reload the changes into the schema.

For example:

Y:\> sqlite3 booktest  
SQLite version 3.7.4  
Enter ".help" for instructions  
Enter SQL statements terminated with a ";"  
sqlite> create table BOOKS ( title TEXT NOT NULL, publication_date TEXT NOT NULL);  
sqlite> insert into BOOKS VALUES ("NULLTEST",null);  
Error: BOOKS.publication_date may not be NULL  
sqlite> PRAGMA writable_schema = 1; 
sqlite> UPDATE SQLITE_MASTER SET SQL = 'CREATE TABLE BOOKS ( title TEXT NOT NULL, publication_date TEXT)' WHERE NAME = 'BOOKS';  
sqlite> PRAGMA writable_schema = 0;  
sqlite> .q  

Y:\> sqlite3 booktest  
SQLite version 3.7.4  
Enter ".help" for instructions  
Enter SQL statements terminated with a ";"  
sqlite> insert into BOOKS VALUES ("NULLTEST",null);  
sqlite> .q  

REFERENCES FOLLOW:


pragma writable_schema
When this pragma is on, the SQLITE_MASTER tables in which database can be changed using ordinary UPDATE, INSERT, and DELETE statements. Warning: misuse of this pragma can easily result in a corrupt database file.

alter table
SQLite supports a limited subset of ALTER TABLE. The ALTER TABLE command in SQLite allows the user to rename a table or to add a new column to an existing table. It is not possible to rename a column, remove a column, or add or remove constraints from a table.

ALTER TABLE SYNTAX

Hydronium
  • 793
  • 1
  • 11
  • 28
Noah
  • 15,080
  • 13
  • 104
  • 148
  • 3
    Dangerous, but still probably the most straight-forward answer imo. – Tek May 18 '12 at 23:13
  • 1
    Although this is dangerous, would it be the best-performing way of renaming a column (better than making a new table, copying the data, and deleting the old table)? Also, is it really that dangerous? It seems prone to mistakes, but unless I'm mistaken, the UPDATE statement is wrapped in a transaction, so it should be safe from sudden power failures, out-of-memory exceptions, etc. – Ethan Jun 07 '12 at 14:28
  • 2
    Yes extremely fast -- *Dangerous* only means "Make sure you have a backup first" – Noah Jun 07 '12 at 16:51
  • 7
    The sqlite file format is very simple and that's why this operation is valid. The file format has only two sets of information about a table: The actual CREATE TABLE command as plain text, and the rows, whose values are appearing in the order of the fields from the CREATE command. Which means that the sqlite code opens the database, it parses each CREATE command and dynamically builds its column information in memory. So, any command that alters the CREATE command in a way that ends up with the same number of columns will work, even if you change their type or constraints. – Thomas Tempelmann Feb 25 '16 at 19:35
  • 3
    @ThomasTempelmann However, adding constraints that are not fulfilled by the dataset will yield to problems because the query planner assumes that constraints hold. – fuz Apr 26 '16 at 20:54
  • @FUZxxl Right, I ran into this myself recently. So I stand corrected: Changing constraints may not be safe using the method of altering the CREATE command directly. – Thomas Tempelmann Apr 28 '16 at 16:56
  • 2
    @ThomasTempelmann *Removing* constraints is always fine. *Adding* constraints is fine if the constraint is satisfied by all rows but you certainly need to check. – fuz Apr 28 '16 at 17:00
  • If you have a large database, especially one that is larger than available disk space, this is the only solution and will be a hell of a lot faster. Do find a way to make a backup though! – drevicko Feb 02 '18 at 08:45
18

CASE 1 : SQLite 3.25.0+

Only the Version 3.25.0 of SQLite supports renaming columns. If your device is meeting this requirement, things are quite simple. The below query would solve your problem:

ALTER TABLE "MyTable" RENAME COLUMN "OldColumn" TO "NewColumn";

CASE 2 : SQLite Older Versions

You have to follow a different Approach to get the result which might be a little tricky

For example, if you have a table like this:

CREATE TABLE student(Name TEXT, Department TEXT, Location TEXT)

And if you wish to change the name of the column Location

Step 1: Rename the original table:

ALTER TABLE student RENAME TO student_temp;

Step 2: Now create a new table student with correct column name:

CREATE TABLE student(Name TEXT, Department TEXT, Address TEXT)

Step 3: Copy the data from the original table to the new table:

INSERT INTO student(Name, Department, Address) SELECT Name, Department, Location FROM student_temp;

Note: The above command should be all one line.

Step 4: Drop the original table:

DROP TABLE student_temp;

With these four steps you can manually change any SQLite table. Keep in mind that you will also need to recreate any indexes, viewers or triggers on the new table as well.

Febin Mathew
  • 991
  • 1
  • 11
  • 20
18

Recently I had to do that in SQLite3 with a table named points with the colunms id, lon, lat. Erroneusly, when the table was imported, the values for latitude where stored in the lon column and viceversa, so an obvious fix would be to rename those columns. So the trick was:

create table points_tmp as select id, lon as lat, lat as lon from points;
drop table points;
alter table points_tmp rename to points;

I hope this would be useful for you!

aizquier
  • 557
  • 5
  • 12
  • 1
    This method does not copy the PK value appropriately and automatically creates the hidden rowid column. Not necessarily a problem but wanted to point that out because it became an issue for me. – TPoschel May 02 '12 at 20:40
  • 4
    Wouldn't it be easier to do "UPDATE points SET lon = lat, lat = lon;"? – kstep Jan 21 '13 at 23:21
  • 1
    This answer does do the process in the correct ORDER. First create the temp table and populate it **then destroy the original**. – Xeoncross Jan 24 '13 at 20:02
14

Quoting the sqlite documentation:

SQLite supports a limited subset of ALTER TABLE. The ALTER TABLE command in SQLite allows the user to rename a table or to add a new column to an existing table. It is not possible to rename a colum, remove a column, or add or remove constraints from a table.

What you can do of course is, create a new table with the new layout, SELECT * FROM old_table, and fill the new table with the values you'll receive.

Elazar Leibovich
  • 32,750
  • 33
  • 122
  • 169
7

First off, this is one of those things that slaps me in the face with surprise: renaming of a column requires creating an entirely new table and copying the data from the old table to the new table...

The GUI I've landed on to do SQLite operations is Base. It's got a nifty Log window that shows all the commands that have been executed. Doing a rename of a column via Base populates the log window with the necessary commands:

Base log window

These can then be easily copied and pasted where you might need them. For me, that's into an ActiveAndroid migration file. A nice touch, as well, is that the copied data only includes the SQLite commands, not the timestamps, etc.

Hopefully, that saves some people time.

Joshua Pinter
  • 45,245
  • 23
  • 243
  • 245
  • FYI, if you *are* using **ActiveAndroid**, you can omit the `BEGIN TRANSACTION;` and `COMMIT;` lines, as ActiveAndroid handles that by itself. – Joshua Pinter May 02 '14 at 23:04
3

change table column < id > to < _id >

 String LastId = "id";

    database.execSQL("ALTER TABLE " + PhraseContract.TABLE_NAME + " RENAME TO " + PhraseContract.TABLE_NAME + "old");
    database.execSQL("CREATE TABLE " + PhraseContract.TABLE_NAME
    +"("
            + PhraseContract.COLUMN_ID + " INTEGER PRIMARY KEY,"
            + PhraseContract.COLUMN_PHRASE + " text ,"
            + PhraseContract.COLUMN_ORDER  + " text ,"
            + PhraseContract.COLUMN_FROM_A_LANG + " text"
    +")"
    );
    database.execSQL("INSERT INTO " +
            PhraseContract.TABLE_NAME + "("+ PhraseContract.COLUMN_ID +" , "+ PhraseContract.COLUMN_PHRASE + " , "+ PhraseContract.COLUMN_ORDER +" , "+ PhraseContract.COLUMN_FROM_A_LANG +")" +
            " SELECT " + LastId +" , "+ PhraseContract.COLUMN_PHRASE + " , "+ PhraseContract.COLUMN_ORDER +" , "+ PhraseContract.COLUMN_FROM_A_LANG +
            " FROM " + PhraseContract.TABLE_NAME + "old");
    database.execSQL("DROP TABLE " + PhraseContract.TABLE_NAME + "old");
Vahe Gharibyan
  • 5,277
  • 4
  • 36
  • 47
3

Create a new column with the desired column name: COLNew.

ALTER TABLE {tableName} ADD COLUMN COLNew {type};

Copy contents of old column COLOld to new column COLNew.

INSERT INTO {tableName} (COLNew) SELECT {COLOld} FROM {tableName}

Note: brackets are necessary in above line.

Anthony Ebert
  • 675
  • 14
  • 25
2

As mentioned before, there is a tool SQLite Database Browser, which does this. Lyckily, this tool keeps a log of all operations performed by the user or the application. Doing this once and looking at the application log, you will see the code involved. Copy the query and paste as required. Worked for me. Hope this helps

2

From the official documentation

A simpler and faster procedure can optionally be used for some changes that do no affect the on-disk content in any way. The following simpler procedure is appropriate for removing CHECK or FOREIGN KEY or NOT NULL constraints, renaming columns, or adding or removing or changing default values on a column.

  1. Start a transaction.

  2. Run PRAGMA schema_version to determine the current schema version number. This number will be needed for step 6 below.

  3. Activate schema editing using PRAGMA writable_schema=ON.

  4. Run an UPDATE statement to change the definition of table X in the sqlite_master table: UPDATE sqlite_master SET sql=... WHERE type='table' AND name='X';

    Caution: Making a change to the sqlite_master table like this will render the database corrupt and unreadable if the change contains a syntax error. It is suggested that careful testing of the UPDATE statement be done on a separate blank database prior to using it on a database containing important data.

  5. If the change to table X also affects other tables or indexes or triggers are views within schema, then run UPDATE statements to modify those other tables indexes and views too. For example, if the name of a column changes, all FOREIGN KEY constraints, triggers, indexes, and views that refer to that column must be modified.

    Caution: Once again, making changes to the sqlite_master table like this will render the database corrupt and unreadable if the change contains an error. Carefully test of this entire procedure on a separate test database prior to using it on a database containing important data and/or make backup copies of important databases prior to running this procedure.

  6. Increment the schema version number using PRAGMA schema_version=X where X is one more than the old schema version number found in step 2 above.

  7. Disable schema editing using PRAGMA writable_schema=OFF.

  8. (Optional) Run PRAGMA integrity_check to verify that the schema changes did not damage the database.

  9. Commit the transaction started on step 1 above.

Mohammad Yahia
  • 483
  • 9
  • 19
1

One option, if you need it done in a pinch, and if your initial column was created with a default, is to create the new column you want, copy the contents over to it, and basically "abandon" the old column (it stays present, but you just don't use/update it, etc.)

ex:

alter table TABLE_NAME ADD COLUMN new_column_name TYPE NOT NULL DEFAULT '';
update TABLE_NAME set new_column_name = old_column_name;
update TABLE_NAME set old_column_name = ''; -- abandon old column, basically

This leaves behind a column (and if it was created with NOT NULL but without a default, then future inserts that ignore it might fail), but if it's just a throwaway table, the tradeoffs might be acceptable. Otherwise use one of the other answers mentioned here, or a different database that allows columns to be renamed.

rogerdpack
  • 62,887
  • 36
  • 269
  • 388
0

need to rename a few columns in some tables

Another way is to use multiple SQLite3 commands to "rename" a column, in "some" tables, repeat as needed:

.output tmp

SELECT "ALTER TABLE """|| sqlite_master.name ||""" RENAME COLUMN old_name TO new_name;" FROM sqlite_master 
WHERE type = "table" AND sqlite_master.name NOT LIKE 'sqlite_%';

.read tmp

source

social
  • 329
  • 3
  • 8
-1

Since version 2018-09-15 (3.25.0) sqlite supports renaming columns

https://sqlite.org/changes.html

RusAlex
  • 8,245
  • 6
  • 36
  • 44
-3

sqlite3 yourdb .dump > /tmp/db.txt
edit /tmp/db.txt change column name in Create line
sqlite2 yourdb2 < /tmp/db.txt
mv/move yourdb2 yourdb

H Bosch
  • 1
  • 1
  • 3
    you're answer doesn't provide any information, a bunch of code/instructions spit out without any extra information on why you think it will work or whats suppose to happen if you run it – RGLSV Mar 04 '15 at 17:41