جين كابت للورم




الجينات الكابحة للأورام هي مورثة ترمز بروتينا ذا دور في التحكم بالنمو الخلوي فتحمي الخلية من تشكل السرطان.[1][2][3] عند تضرر هذه المورثة أو تثبيطها، قد تتطور الخلية إلى سرطان، غالبا بعد التعرض لعوامل معينة. من الأمثلة عليها مورثة APC ومورثة RB وبي53.



مراجع




  1. ^ Yoshida BA، Sokoloff MM، Welch DR، Rinker-Schaeffer CW (November 2000). "Metastasis-suppressor genes: a review and perspective on an emerging field". J. Natl. Cancer Inst. 92 (21): 1717–30. PMID 11058615. doi:10.1093/jnci/92.21.1717. 


  2. ^ Baker SJ، Markowitz S، Fearon ER، Willson JK، Vogelstein B (1990). "Suppression of human colorectal carcinoma cell growth by wild-type p53". Science. 249 (4971): 912–5. PMID 2144057. doi:10.1126/science.2144057. 


  3. ^ Sherr CJ (January 2004). "Principles of tumor suppression". Cell. 116 (2): 235–46. PMID 14744434. doi:10.1016/S0092-8674(03)01075-4. 



انظر أيضا


  • جين ورمي




مصادر طبية



  • جايستور: tumor-suppressor-proteins 


  • MeSH ID: D016147 



  • أيقونة بوابةبوابة علم الأحياء الخلوي والجزيئي


  • أيقونة بوابةبوابة طب



Star of life.svg
هذه بذرة مقالة عن العلوم الطبية بحاجة للتوسيع. شارك في تحريرها.



مشاريع شقيقة
في كومنز صور وملفات عن: جين كابت للورم








-

Popular posts from this blog

SQL Server 17 - Attemping to backup to remote NAS but Access is denied

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0; } 0 I was attemping to use Ola Hallengrens scripts to backup to a remote NAS, but it was failing and not giving any direct errors, so I tried doing it manually using Server Management Studio and got the following error: TITLE: Microsoft SQL Server Management Studio Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476 ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The operating system returned the error '0x80070005(Access is denied.)&#
Read more

Always On Availability groups resolving state after failover - Remote harden of transaction...

Image
0 My explanation will be opinion based as it is based on my findings. If more information is needed, I am always happy to add it. The setup We have 4 SQL Server 2016 Instances, and all 4 underlying servers are in a WSFC (In my eyes a strange setup since Always On AG's are 2 by 2. But that is a different question.) 4 nodes + Fileshare witness Version: 13.0.5026.0 (all nodes) The instances that are having the failover issues are instances 1 & 2. They have 3 AG's between them. AG1 is primary on instance 1 and is having the issue. AG2 and AG3 are primary on instance 2. Instances 3 and 4 have their own separate AG's (2). AG1's settings The week before Last week, after checking for long running queries (none) and the synchronization state (green accross the board) we initiated a
Read more

Restoring from pg_dump with foreign key constraints

Image
5 2 In restoring a database from a pg_dump , a number of errors are being generated and the whole table is subsequently being ignored. An example: ERROR: insert or update on table "channelproducts" violates foreign key constraint "fk_rails_dfaae373a5" DETAIL: Key (channel_id)=(1) is not present in table "channels". Interestingly enough, I've noted that all these instances are popping up because of the sequence of loading. channels is after channelproducts both alphabetically and in the file and thus I can understand why postgres complains about having to create a child without a parent. caveat: the foreign key is being generated automatically by rails 4.2: I could remove the problem at the source but that still does not really solve the problem... version: PostgreSQL
Read more