About: Transaction log is a research topic. Over the lifetime, 1651 publications have been published within this topic receiving 41743 citations. The topic is also known as: database log & transaction journal.
TL;DR: A failure analysis was conducted, identifying trends among user mistakes, and a summary of findings and a discussion of the implications of these findings were concluded.
Abstract: We analyzed transaction logs containing 51,473 queries posed by 18,113 users of Excite, a major Internet search service. We provide data on: (i) sessions — changes in queries during a session, number of pages viewed, and use of relevance feedback; (ii) queries — the number of search terms, and the use of logic and modifiers; and (iii) terms — their rank/frequency distribution and the most highly used search terms. We then shift the focus of analysis from the query to the user to gain insight to the characteristics of the Web user. With these characteristics as a basis, we then conducted a failure analysis, identifying trends among user mistakes. We conclude with a summary of findings and a discussion of the implications of these findings. # 2000 Elsevier Science Ltd. All rights reserved.
TL;DR: The Bitcoin protocol as mentioned in this paper is an online communication protocol that facilitates the use of virtual currency, including electronic payments, and allows for irreversible transactions, a prescribed path of money creation over time, and a public transaction history.
Abstract: Bitcoin is an online communication protocol that facilitates the use of a virtual currency, including electronic payments. Bitcoin's rules were designed by engineers with no apparent influence from lawyers or regulators. Bitcoin is built on a transaction log that is distributed across a network of participating computers. It includes mechanisms to reward honest participation, to bootstrap acceptance by early adopters, and to guard against concentrations of power. Bitcoin's design allows for irreversible transactions, a prescribed path of money creation over time, and a public transaction history. Anyone can create a Bitcoin account, without charge and without any centralized vetting procedure—or even a requirement to provide a real name. Collectively, these rules yield a system that is understood to be more flexible, more private, and less amenable to regulatory oversight than other forms of payment—though as we discuss, all these benefits face important limits. Bitcoin is of interest to economis...
TL;DR: In this paper, a method for collecting, storing, and retrieving data in a database management system is presented, where a transaction file corresponding to the transaction in an outbox of a workgroup user client is copied to an inbox identified to the workgroup client.
Abstract: A method of and system for collecting, storing, and retrieving data in a database management system. The database management system includes a master database server (4), at least one workgroup server (315), and a plurality of workgroup user clients (310). The workgroup server (315) is interposed between the master database server (4) and said workgroup user clients (310). The method creating a transaction in a local database resident on one of the workgroup user clients (310), entering the transaction into a transaction log resident on the workgroup user client (310), and creating a transaction file corresponding to the transaction in an outbox of said workgroup user client (310). Next, the transaction file is copied to an inbox identified to the workgroup user client (310) and updating the transaction file into a workgroup database (305) resident on the workgroup server (315). The workgroup database (305) includes a transaction log.
TL;DR: An incremental approach to check the conformance of a process model and an event log is proposed and a Conformance Checker has been implemented within the ProM framework and it has been evaluated using artificial and real-life event logs.
TL;DR: In this paper, the authors present a method for collecting, storing, and retrieving data in a database management system, which includes creating a transaction in a local database resident on a workgroup user client, entering the transaction into a transaction log resident on the work group user client and creating transaction file corresponding to the transaction log in an outbox of the workgroup users client.
Abstract: Method of and apparatus for collecting, storing, and retrieving data in a database management system. The database management system has an enterprise server and at least one workgroup user client. The method includes creating a transaction in a local database resident on said workgroup user client, entering the transaction into a transaction log resident on the workgroup user client, and creating a transaction file corresponding to the transaction log in an outbox of the workgroup user client. The workgroup user client transaction log is read, skipping those transactions which originate at the enterprise server, data files are created corresponding to the entries. The data files corresponding to transactions originating at the workgroup user client are read to an inbox on the enterprise server, thus updating the transactions into an enterprise database on the enterprise server.