Skip to main content

PL/SQL Adding Columns to a Table without Loosing any Data

-- Renaming the last 4 column names
alter table TEST_TABLE_NAME rename column KAYIT_KULLANICI_ID to XKAYIT_KULLANICI_ID;
alter table TEST_TABLE_NAME rename column KAYIT_TARIHI to XKAYIT_TARIHI;
alter table TEST_TABLE_NAME rename column GUNCELLEME_KULLANICI_ID to XGUNCELLEME_KULLANICI_ID;
alter table TEST_TABLE_NAME rename column GUNCELLEME_TARIHI to XGUNCELLEME_TARIHI;
alter table TEST_TABLE_NAME drop CONSTRAINT "FK_TEST_TABLE_GNC_KULL_ID";
alter table TEST_TABLE_NAME drop CONSTRAINT "FK_TEST_TABLE_KYT_KULL_ID";

-- Adding new columns
alter table TEST_TABLE_NAME add "SICIL_NO"    VARCHAR2(20 BYTE);
alter table TEST_TABLE_NAME add "ACIKLAMA" VARCHAR2(200 BYTE);

-- Adding new "last 4 fields" which were renamed at the beginning
alter table TEST_TABLE_NAME add "KAYIT_KULLANICI_ID" NUMBER(18,0);
alter table TEST_TABLE_NAME add "KAYIT_TARIHI" DATE;
alter table TEST_TABLE_NAME add "GUNCELLEME_KULLANICI_ID" NUMBER(18,0);
alter table TEST_TABLE_NAME add "GUNCELLEME_TARIHI" DATE;

-- Updating new "last 4 fields" from ex- "last 4 fields"
update TEST_TABLE_NAME set
KAYIT_KULLANICI_ID = XKAYIT_KULLANICI_ID,
KAYIT_TARIHI = XKAYIT_TARIHI,
GUNCELLEME_KULLANICI_ID = XGUNCELLEME_KULLANICI_ID,
GUNCELLEME_TARIHI = XGUNCELLEME_TARIHI;

-- New "last 4 fields" are being made "not nullable"
alter table TEST_TABLE_NAME modify "KAYIT_KULLANICI_ID" NUMBER(18,0) NOT NULL ENABLE;
alter table TEST_TABLE_NAME modify "KAYIT_TARIHI" DATE DEFAULT sysdate NOT NULL ENABLE;
alter table TEST_TABLE_NAME add CONSTRAINT "FK_TEST_TABLE_GNC_KULL_ID" FOREIGN KEY ("GUNCELLEME_KULLANICI_ID")
REFERENCES "SCHEMA_NAME"."TEST_TABLE_NAME_2" ("ID") ENABLE;
alter table TEST_TABLE_NAME add CONSTRAINT "FK_TEST_TABLE_KYT_KULL_ID" FOREIGN KEY ("KAYIT_KULLANICI_ID")
REFERENCES "SCHEMA_NAME"."TEST_TABLE_NAME_2" ("ID") ENABLE;

-- Dropping ex-"last 4 fields"
alter table TEST_TABLE_NAME drop column "XKAYIT_KULLANICI_ID";
alter table TEST_TABLE_NAME drop column "XKAYIT_TARIHI";
alter table TEST_TABLE_NAME drop column "XGUNCELLEME_KULLANICI_ID";
alter table TEST_TABLE_NAME drop column "XGUNCELLEME_TARIHI";

Comments

Popular posts from this blog

How to fix Git push error: "RPC failed; curl 56 HTTP/2 stream 7 was reset send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly"

Problem Today I saw the following problem when I tried to push my changes to a Git server after doing some work for upgrading an Umbraco v7 project to v8.18.8.  Possible reasons After some investigations, it seems like this could be because of the following reasons; Git is not happy with the amount of changes that are being pushed into the server.  There are possible limitations on the server about the size/amount of files that you can push. Your internet connection is not good and stable enough. Your Git client's version is old. Solution options For me, the easiest option was connecting to another Wifi and trying again. Apparently, this option helped quite a few people, so it is worth giving it a try. Unfortunately, it didn't work for me. A bad internet connection wasn't an option for me either, as my internet is pretty fast (500 Mbps). Similarly, my Git client version was the latest version (git version 2.41.0.windows.3).  On StackOverflow, there were a lot of recommend...

How to fix "Microsoft SQL Error SQL71564: Error validating element [USERNAME]: The element [USERNAME] has been orphaned from its login and cannot be deployed."

I needed to export a database in BACPAC format today in order to restore it somewhere else, and I encountered the following error. To resolve this issue, I deleted all of the users mentioned in the error log. After successfully creating the BACPAC file, I used it to create a new database with no problems. Error: TITLE: Microsoft SQL Server Management Studio ------------------------------ One or more unsupported elements were found in the schema used as part of a data package. Error SQL71564: Error validating element [USER1]: The element [USER1] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER2]: The element [USER2] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER3]: The element [USER3] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER4]: The element [USER4] has been orphaned from its login and cannot be deployed. Error SQL71...

How to use JQuery Ajax Methods for Async ASP.NET MVC Action Methods

Making repeatedly calls to async methods can be a nightmare. In this case, it makes sense to use 2 ajax methods, instead of one. Here is a simple solution to overcome this problem. See that  ajaxcalls   is emptied after the success response for the first ajax call and then the second ajax method is used to make one single call to the async action method. Hope it helps. View: @section Scripts{     < script type ="text/javascript">         var smartDebitObject = new Object();         smartDebitObject.MembershipNumber = $( "#MembershipNumber" ).val();         smartDebitObject.ProfileId = $( "#ProfileId" ).val();         smartDebitObject.FirstName = $( "#FirstName" ).val();         smartDebitObject.LastName = $( "#LastName" ).val();     ...