An Introduction to the Acid Dossociation Constant (Pka)
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Not ACID, Not BASE, but SALT a Transaction Processing Perspective on Blockchains
Not ACID, not BASE, but SALT A Transaction Processing Perspective on Blockchains Stefan Tai, Jacob Eberhardt and Markus Klems Information Systems Engineering, Technische Universitat¨ Berlin fst, je, [email protected] Keywords: SALT, blockchain, decentralized, ACID, BASE, transaction processing Abstract: Traditional ACID transactions, typically supported by relational database management systems, emphasize database consistency. BASE provides a model that trades some consistency for availability, and is typically favored by cloud systems and NoSQL data stores. With the increasing popularity of blockchain technology, another alternative to both ACID and BASE is introduced: SALT. In this keynote paper, we present SALT as a model to explain blockchains and their use in application architecture. We take both, a transaction and a transaction processing systems perspective on the SALT model. From a transactions perspective, SALT is about Sequential, Agreed-on, Ledgered, and Tamper-resistant transaction processing. From a systems perspec- tive, SALT is about decentralized transaction processing systems being Symmetric, Admin-free, Ledgered and Time-consensual. We discuss the importance of these dual perspectives, both, when comparing SALT with ACID and BASE, and when engineering blockchain-based applications. We expect the next-generation of decentralized transactional applications to leverage combinations of all three transaction models. 1 INTRODUCTION against. Using the admittedly contrived acronym of SALT, we characterize blockchain-based transactions There is a common belief that blockchains have the – from a transactions perspective – as Sequential, potential to fundamentally disrupt entire industries. Agreed, Ledgered, and Tamper-resistant, and – from Whether we are talking about financial services, the a systems perspective – as Symmetric, Admin-free, sharing economy, the Internet of Things, or future en- Ledgered, and Time-consensual. -
Failures in DBMS
Chapter 11 Database Recovery 1 Failures in DBMS Two common kinds of failures StSystem filfailure (t)(e.g. power outage) ‒ affects all transactions currently in progress but does not physically damage the data (soft crash) Media failures (e.g. Head crash on the disk) ‒ damagg()e to the database (hard crash) ‒ need backup data Recoveryyp scheme responsible for handling failures and restoring database to consistent state 2 Recovery Recovering the database itself Recovery algorithm has two parts ‒ Actions taken during normal operation to ensure system can recover from failure (e.g., backup, log file) ‒ Actions taken after a failure to restore database to consistent state We will discuss (briefly) ‒ Transactions/Transaction recovery ‒ System Recovery 3 Transactions A database is updated by processing transactions that result in changes to one or more records. A user’s program may carry out many operations on the data retrieved from the database, but the DBMS is only concerned with data read/written from/to the database. The DBMS’s abstract view of a user program is a sequence of transactions (reads and writes). To understand database recovery, we must first understand the concept of transaction integrity. 4 Transactions A transaction is considered a logical unit of work ‒ START Statement: BEGIN TRANSACTION ‒ END Statement: COMMIT ‒ Execution errors: ROLLBACK Assume we want to transfer $100 from one bank (A) account to another (B): UPDATE Account_A SET Balance= Balance -100; UPDATE Account_B SET Balance= Balance +100; We want these two operations to appear as a single atomic action 5 Transactions We want these two operations to appear as a single atomic action ‒ To avoid inconsistent states of the database in-between the two updates ‒ And obviously we cannot allow the first UPDATE to be executed and the second not or vice versa. -
SQL Vs Nosql: a Performance Comparison
SQL vs NoSQL: A Performance Comparison Ruihan Wang Zongyan Yang University of Rochester University of Rochester [email protected] [email protected] Abstract 2. ACID Properties and CAP Theorem We always hear some statements like ‘SQL is outdated’, 2.1. ACID Properties ‘This is the world of NoSQL’, ‘SQL is still used a lot by We need to refer the ACID properties[12]: most of companies.’ Which one is accurate? Has NoSQL completely replace SQL? Or is NoSQL just a hype? SQL Atomicity (Structured Query Language) is a standard query language A transaction is an atomic unit of processing; it should for relational database management system. The most popu- either be performed in its entirety or not performed at lar types of RDBMS(Relational Database Management Sys- all. tems) like Oracle, MySQL, SQL Server, uses SQL as their Consistency preservation standard database query language.[3] NoSQL means Not A transaction should be consistency preserving, meaning Only SQL, which is a collection of non-relational data stor- that if it is completely executed from beginning to end age systems. The important character of NoSQL is that it re- without interference from other transactions, it should laxes one or more of the ACID properties for a better perfor- take the database from one consistent state to another. mance in desired fields. Some of the NOSQL databases most Isolation companies using are Cassandra, CouchDB, Hadoop Hbase, A transaction should appear as though it is being exe- MongoDB. In this paper, we’ll outline the general differences cuted in iso- lation from other transactions, even though between the SQL and NoSQL, discuss if Relational Database many transactions are execut- ing concurrently. -
101 Lime Solvent
Sure Klean® CLEANING & PROTECTIVE TREATMENTS 101 Lime Solvent Sure Klean® 101 Lime Solvent is a concentrated acidic cleaner for dark-colored brick and tile REGULATORY COMPLIANCE surfaces which are not subject to metallic oxidation. VOC Compliance Safely removes excess mortar and construction dirt. Sure Klean® 101 Lime Solvent is compliant with all national, state and district VOC regulations. ADVANTAGES • Removes construction dirt and excess mortar with TYPICAL TECHNICAL DATA simple cold water rinse. Clear, brown liquid • Removes efflorescence from new brick and new FORM Pungent odor stone construction. SPECIFIC GRAVITY 1.12 • Safer than muriatic acid on colored mortar and dark-colored new masonry surfaces. pH 0.50 @ 1:6 dilution • Proven effective since 1954. WT/GAL 9.39 lbs Limitations ACTIVE CONTENT not applicable • Not generally effective in removal of atmospheric TOTAL SOLIDS not applicable stains and black carbon found on older masonry VOC CONTENT not applicable surfaces. Use the appropriate Sure Klean® FLASH POINT not applicable restoration cleaner to remove atmospheric staining from older masonry surfaces. FREEZE POINT <–22° F (<–30° C) • Not for use on polished natural stone. SHELF LIFE 3 years in tightly sealed, • Not for use on treated low-E glass; acrylic and unopened container polycarbonate sheet glazing; and glazing with surface-applied reflective, metallic or other synthetic coatings and films. SAFETY INFORMATION Always read full label and SDS for precautionary instructions before use. Use appropriate safety equipment and job site controls during application and handling. 24-Hour Emergency Information: INFOTRAC at 800-535-5053 Product Data Sheet • Page 1 of 4 • Item #10010 – 102715 • ©2015 PROSOCO, Inc. -
APPENDIX G Acid Dissociation Constants
harxxxxx_App-G.qxd 3/8/10 1:34 PM Page AP11 APPENDIX G Acid Dissociation Constants § ϭ 0.1 M 0 ؍ (Ionic strength ( † ‡ † Name Structure* pKa Ka pKa ϫ Ϫ5 Acetic acid CH3CO2H 4.756 1.75 10 4.56 (ethanoic acid) N ϩ H3 ϫ Ϫ3 Alanine CHCH3 2.344 (CO2H) 4.53 10 2.33 ϫ Ϫ10 9.868 (NH3) 1.36 10 9.71 CO2H ϩ Ϫ5 Aminobenzene NH3 4.601 2.51 ϫ 10 4.64 (aniline) ϪO SNϩ Ϫ4 4-Aminobenzenesulfonic acid 3 H3 3.232 5.86 ϫ 10 3.01 (sulfanilic acid) ϩ NH3 ϫ Ϫ3 2-Aminobenzoic acid 2.08 (CO2H) 8.3 10 2.01 ϫ Ϫ5 (anthranilic acid) 4.96 (NH3) 1.10 10 4.78 CO2H ϩ 2-Aminoethanethiol HSCH2CH2NH3 —— 8.21 (SH) (2-mercaptoethylamine) —— 10.73 (NH3) ϩ ϫ Ϫ10 2-Aminoethanol HOCH2CH2NH3 9.498 3.18 10 9.52 (ethanolamine) O H ϫ Ϫ5 4.70 (NH3) (20°) 2.0 10 4.74 2-Aminophenol Ϫ 9.97 (OH) (20°) 1.05 ϫ 10 10 9.87 ϩ NH3 ϩ ϫ Ϫ10 Ammonia NH4 9.245 5.69 10 9.26 N ϩ H3 N ϩ H2 ϫ Ϫ2 1.823 (CO2H) 1.50 10 2.03 CHCH CH CH NHC ϫ Ϫ9 Arginine 2 2 2 8.991 (NH3) 1.02 10 9.00 NH —— (NH2) —— (12.1) CO2H 2 O Ϫ 2.24 5.8 ϫ 10 3 2.15 Ϫ Arsenic acid HO As OH 6.96 1.10 ϫ 10 7 6.65 Ϫ (hydrogen arsenate) (11.50) 3.2 ϫ 10 12 (11.18) OH ϫ Ϫ10 Arsenious acid As(OH)3 9.29 5.1 10 9.14 (hydrogen arsenite) N ϩ O H3 Asparagine CHCH2CNH2 —— —— 2.16 (CO2H) —— —— 8.73 (NH3) CO2H *Each acid is written in its protonated form. -
Drugs and Acid Dissociation Constants Ionisation of Drug Molecules Most Drugs Ionise in Aqueous Solution.1 They Are Weak Acids Or Weak Bases
Drugs and acid dissociation constants Ionisation of drug molecules Most drugs ionise in aqueous solution.1 They are weak acids or weak bases. Those that are weak acids ionise in water to give acidic solutions while those that are weak bases ionise to give basic solutions. Drug molecules that are weak acids Drug molecules that are weak bases where, HA = acid (the drug molecule) where, B = base (the drug molecule) H2O = base H2O = acid A− = conjugate base (the drug anion) OH− = conjugate base (the drug anion) + + H3O = conjugate acid BH = conjugate acid Acid dissociation constant, Ka For a drug molecule that is a weak acid The equilibrium constant for this ionisation is given by the equation + − where [H3O ], [A ], [HA] and [H2O] are the concentrations at equilibrium. In a dilute solution the concentration of water is to all intents and purposes constant. So the equation is simplified to: where Ka is the acid dissociation constant for the weak acid + + Also, H3O is often written simply as H and the equation for Ka is usually written as: Values for Ka are extremely small and, therefore, pKa values are given (similar to the reason pH is used rather than [H+]. The relationship between pKa and pH is given by the Henderson–Hasselbalch equation: or This relationship is important when determining pKa values from pH measurements. Base dissociation constant, Kb For a drug molecule that is a weak base: 1 Ionisation of drug molecules. 1 Following the same logic as for deriving Ka, base dissociation constant, Kb, is given by: and Ionisation of water Water ionises very slightly. -
Solvent Effects on the Thermodynamic Functions of Dissociation of Anilines and Phenols
University of Wollongong Research Online University of Wollongong Thesis Collection 1954-2016 University of Wollongong Thesis Collections 1982 Solvent effects on the thermodynamic functions of dissociation of anilines and phenols Barkat A. Khawaja University of Wollongong Follow this and additional works at: https://ro.uow.edu.au/theses University of Wollongong Copyright Warning You may print or download ONE copy of this document for the purpose of your own research or study. The University does not authorise you to copy, communicate or otherwise make available electronically to any other person any copyright material contained on this site. You are reminded of the following: This work is copyright. Apart from any use permitted under the Copyright Act 1968, no part of this work may be reproduced by any process, nor may any other exclusive right be exercised, without the permission of the author. Copyright owners are entitled to take legal action against persons who infringe their copyright. A reproduction of material that is protected by copyright may be a copyright infringement. A court may impose penalties and award damages in relation to offences and infringements relating to copyright material. Higher penalties may apply, and higher damages may be awarded, for offences and infringements involving the conversion of material into digital or electronic form. Unless otherwise indicated, the views expressed in this thesis are those of the author and do not necessarily represent the views of the University of Wollongong. Recommended Citation Khawaja, Barkat A., Solvent effects on the thermodynamic functions of dissociation of anilines and phenols, Master of Science thesis, Department of Chemistry, University of Wollongong, 1982. -
Solvent-Tunable Binding of Hydrophilic and Hydrophobic Guests by Amphiphilic Molecular Baskets Yan Zhao Iowa State University, [email protected]
Chemistry Publications Chemistry 8-2005 Solvent-Tunable Binding of Hydrophilic and Hydrophobic Guests by Amphiphilic Molecular Baskets Yan Zhao Iowa State University, [email protected] Eui-Hyun Ryu Iowa State University Follow this and additional works at: http://lib.dr.iastate.edu/chem_pubs Part of the Chemistry Commons The ompc lete bibliographic information for this item can be found at http://lib.dr.iastate.edu/ chem_pubs/197. For information on how to cite this item, please visit http://lib.dr.iastate.edu/ howtocite.html. This Article is brought to you for free and open access by the Chemistry at Iowa State University Digital Repository. It has been accepted for inclusion in Chemistry Publications by an authorized administrator of Iowa State University Digital Repository. For more information, please contact [email protected]. Solvent-Tunable Binding of Hydrophilic and Hydrophobic Guests by Amphiphilic Molecular Baskets Abstract Responsive amphiphilic molecular baskets were obtained by attaching four facially amphiphilic cholate groups to a tetraaminocalixarene scaffold. Their binding properties can be switched by solvent changes. In nonpolar solvents, the molecules utilize the hydrophilic faces of the cholates to bind hydrophilic molecules such as glucose derivatives. In polar solvents, the molecules employ the hydrophobic faces of the cholates to bind hydrophobic guests. A water-soluble basket can bind polycyclic aromatic hydrocarbons including anthracene, pyrene, and perylene. The binding free energy (−ΔG) ranges from 5 to 8 kcal/mol and is directly proportional to the surface area of the aromatic hosts. Binding of both hydrophilic and hydrophobic guests is driven by solvophobic interactions. Disciplines Chemistry Comments Reprinted (adapted) with permission from Journal of Organic Chemistry 70 (2005): 7585, doi:10.1021/ jo051127f. -
I. the Nature of Solutions
Solutions The Nature of Solutions Definitions Solution - homogeneous mixture Solute - substance being dissolved Solvent - present in greater amount Types of Solutions SOLUTE – the part of a Solute Solvent Example solution that is being dissolved (usually the solid solid ? lesser amount) solid liquid ? SOLVENT – the part of a solution that gas solid ? dissolves the solute (usually the greater liquid liquid ? amount) gas liquid ? Solute + Solvent = Solution gas gas ? Is it a Solution? Homogeneous Mixture (Solution) Tyndall no Effect? Solution Is it a Solution? Solution • homogeneous • very small particles • no Tyndall effect • particles don’t settle • Ex: •rubbing alcohol Is it a Solution? Homogeneous Mixture (Solution) Tyndall no Effect? yes Solution Suspension, Colloid, or Emulsion Will mixture separate if allowed to stand? no Colloid (very fine solid in liquid) Is it a Solution? Colloid • homogeneous • very fine particles • Tyndall effect • particles don’t settle • Ex: •milk Is it a Solution? Homogeneous Mixture (Solution) Tyndall Effect? no yes Solution Suspension, Colloid, or Emulsion Will mixture separate if allowed to stand? no yes Colloid Suspension or Emulsion Solid or liquid particles? solid Suspension (course solid in liquid) Is it a Solution? Suspension • homogeneous • large particles • Tyndall effect • particles settle if given enough time • Ex: • Pepto-Bismol • Fresh-squeezed lemonade Is it a Solution? Homogeneous Mixture (Solution) Tyndall no Effect? yes Solution Suspension, Colloid, or Emulsion Will mixture separate if allowed to stand? no yes Colloid Suspension or Emulsion Solid or liquid particles? solid liquid Suspension (course solid in liquid) Emulsion (liquid in liquid) Is it a Solution? Emulsion • homogeneous • mixture of two immiscible liquids • Tyndall effect • particles settle if given enough time • Ex: • Mayonnaise Pure Substances vs. -
Chapter 18 Solutions and Their Behavior
Chapter 18 Solutions and Their Behavior 18.1 Properties of Solutions Lesson Objectives The student will: • define a solution. • describe the composition of solutions. • define the terms solute and solvent. • identify the solute and solvent in a solution. • describe the different types of solutions and give examples of each type. • define colloids and suspensions. • explain the differences among solutions, colloids, and suspensions. • list some common examples of colloids. Vocabulary • colloid • solute • solution • solvent • suspension • Tyndall effect Introduction In this chapter, we begin our study of solution chemistry. We all might think that we know what a solution is, listing a drink like tea or soda as an example of a solution. What you might not have realized, however, is that the air or alloys such as brass are all classified as solutions. Why are these classified as solutions? Why wouldn’t milk be classified as a true solution? To answer these questions, we have to learn some specific properties of solutions. Let’s begin with the definition of a solution and look at some of the different types of solutions. www.ck12.org 394 E-Book Page 402 Homogeneous Mixtures A solution is a homogeneous mixture of substances (the prefix “homo-” means “same”), meaning that the properties are the same throughout the solution. Take, for example, the vinegar that is used in cooking. Vinegar is approximately 5% acetic acid in water. This means that every teaspoon of vinegar contains 5% acetic acid and 95% water. When a solution is said to have uniform properties, the definition is referring to properties at the particle level. -
Implementing Distributed Transactions Distributed Transaction Distributed Database Systems ACID Properties Global Atomicity Atom
Distributed Transaction • A distributed transaction accesses resource managers distributed across a network Implementing Distributed • When resource managers are DBMSs we refer to the Transactions system as a distributed database system Chapter 24 DBMS at Site 1 Application Program DBMS 1 at Site 2 2 Distributed Database Systems ACID Properties • Each local DBMS might export • Each local DBMS – stored procedures, or – supports ACID properties locally for each subtransaction – an SQL interface. • Just like any other transaction that executes there • In either case, operations at each site are grouped – eliminates local deadlocks together as a subtransaction and the site is referred • The additional issues are: to as a cohort of the distributed transaction – Global atomicity: all cohorts must abort or all commit – Each subtransaction is treated as a transaction at its site – Global deadlocks: there must be no deadlocks involving • Coordinator module (part of TP monitor) supports multiple sites ACID properties of distributed transaction – Global serialization: distributed transaction must be globally serializable – Transaction manager acts as coordinator 3 4 Atomic Commit Protocol Global Atomicity Transaction (3) xa_reg • All subtransactions of a distributed transaction Manager Resource must commit or all must abort (coordinator) Manager (1) tx_begin (cohort) • An atomic commit protocol, initiated by a (4) tx_commit (5) atomic coordinator (e.g., the transaction manager), commit protocol ensures this. (3) xa_reg Resource Application – Coordinator -
Write-Ahead Logging (WAL) Protocol
CSC 261/461 – Database Systems Lecture 23 Fall 2017 CSC 261, Fall 2017, UR Announcements • Project 3 Due on: 12/01 • Poster: – Will be viewed by the whole department – Even, you may present it later – So, make sure, there is no typo and no embarrassing error. – Go through the poster multiple times – Strongly recommended: • Send us a copy by Sunday. We will try to give you quick feedback. • You can send the poster for printing on Tuesday CSC 261, Fall 2017, UR Today’s Lecture 1. Transactions 2. Properties of Transactions: ACID 3. Logging CSC 261, Fall 2017, UR TRANSACTIONS CSC 261, Fall 2017, UR Transactions: Basic Definition A transaction (“TXN”) is a sequence In the real world, a TXN of one or more operations (reads or either happened writes) which reflects a single real- completely or not at all world transition. START TRANSACTION UPDATE Product SET Price = Price – 1.99 WHERE pname = ‘Gizmo’ COMMIT CSC 261, Fall 2017, UR Transactions: Basic Definition A transaction (“TXN”) is a sequence of one or In the real world, a TXN more operations (reads or writes) which either happened reflects a single real-world transition. completely or not at all Examples: • Transfer money between accounts • Purchase a group of products • Register for a class (either waitlist or allocated) CSC 261, Fall 2017, UR Transactions in SQL • In “ad-hoc” SQL: – Default: each statement = one transaction • In a program, multiple statements can be grouped together as a transaction: START TRANSACTION UPDATE Bank SET amount = amount – 100 WHERE name = ‘Bob’ UPDATE Bank SET amount = amount + 100 WHERE name = ‘Joe’ COMMIT CSC 261, Fall 2017, UR Motivation for Transactions Grouping user actions (reads & writes) into transactions helps with two goals: 1.