Last updated: 2019-04-30 12:36:02 +0200
Date: 2009-02-03 20:00:33 +0100
RENAME COLUMN through SQL
Date: 2009-04-28 13:33:43 +0200
ALTER TABLE xxx RENAME [ COLUMN ] yyy TO zzz
Date: 2009-12-04 11:33:54 +0100
seems long hanging fruit.
Date: 2010-05-04 09:32:09 +0200
This bug was previously known as tracker item 2561693 at http://sourceforge.net/support/tracker.php?aid=2561693
Date: 2011-01-31 14:26:48 +0100
Created attachment 50
This patch contains the work done so far, it actually breaks on the gdk logger, where I cannot do the rename thing.
Date: 2012-03-15 08:00:29 +0100
I have made yesterday the second serious attempt to move our application from Postgres to Monet. I have met two show-stopper issues which put an end to this:
It is nice that Monet is 20 times faster than Postgres for reads (and 30 times slower for writes), but the SQL is just too limited.
Date: 2012-03-15 09:06:13 +0100
This rather looks like a feature request that a bug report to me.
Date: 2012-03-15 09:09:24 +0100
As an alternative to renaming tables or columns, using views and handling name mappings in the application could be considered.
Date: 2012-03-15 13:11:39 +0100
(In reply to comment 7)
This enhancement request was first filled Feb 2009, 3 years and 1 month ago. Wouldn't you say it is more effective that you add a small feature implemented by most common databases, such as Postgres, MySQL, MSSQL, etc, rather than force your users to use difficult and kludgy workarounds? Renaming columns and tables are basic operations, not rocket science.
Date: 2012-03-15 13:14:32 +0100
Problem is that even though it seems easy to do, in fact it is not, since at a critical level columns cannot be renamed. The partial patch basically went that way and it won't work. There might be more luck in an approach that drops the column, but sneakily keeps the data around, then creates a new column, and sneakily attaches the saved data again.
Date: 2016-10-24 23:16:07 +0200
I am just now sorely missing this feature. Scenario: You've loaded a very large amount of data into a DB table, and the original files are gone. Do you really have to recreate the entire table just for a column rename? Surely that can't be right.
By the way...
Date: 2018-11-07 11:56:29 +0100
A new SQL statement will be available in the next feature release of MonetDB for renaming columns:
ALTER TABLE [IF EXISTS] [schemaname.]tablename RENAME [COLUMN] oldname TO newname;
We did this by adding a new entry in the GDK logger referencing the name change of a SQL object, thus no moving data occurs.
Date: 2019-01-21 15:38:15 +0100
This should be in the next feature release.
The text was updated successfully, but these errors were encountered: