You might have seen the recent news reports about the collision between U.S. and Russian communication satellites. The U.S. satellite was one of the Iridium satellites. What wasn’t reported and you probably don’t know is that an object database management system (ODBMS) is an important part of the Iridium system. Even though ODBMSs are a [...]
February 13, 2009
I am now also posting on the Cutter Blog. My initial posting is (The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services. It is a response to Anne Thomas Manes’ SOA is Dead; Long Live Services on her blog at the Burton Group.
January 9, 2009
The typical definition of an atomic task or process is one that cannot be decomposed further. This is vague and subject to interpretation. The Decomposition Matrix on this site uses a specific definition: A task (for business process diagrams) or a process (for data flow diagrams) is atomic if every input relates to every output [...]
December 3, 2008
My last posting referenced the criteria for a well-formed business process diagram mentioned in Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. I am going to expand on their criteria to create a more comprehensive definition of a well-formed business process diagram.
To start, here are three criteria from [...]
November 18, 2008
I recently received two new books on business process modeling. Both books looked interesting because they had great titles. As it turns out, one book is great and the other not so good.
The not so good book is Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. There are [...]
October 9, 2008
The Design Decomposition Blog is written by Doug Barry.
There are three JDO identity models to allow for different underlying database
management systems (DBMSs). The type of JDO identity used is a property of a JDO PersistenceCapable class.
The JDO identity models are:
Application (primary key) identity. This is the JDO identity type used for data stores in which the
value(s) in the instance
determine the identity of the object in the data store. (This is commonly
used in relational DBMSs)
Data store identity. This is the JDO identity type used for data stores in which the identity of the data in the
data store does not depend on the values in the instance. The implementation guarantees
uniqueness for all instances. (This is commonly used in object DBMSs.)
Non-data store JDO identity. The primary usage for non-data store JDO identity is for log files, history files, and other
similar files, where performance is a primary concern.
A JDO implementation is required to support either application (primary key) identity or
datastore identity, and may optionally support non-datastore identity.
There are nearly 400 pages of articles on this site with over 40 pages on database concepts and standards.
Search this site for more articles
Custom Search
Browse this site for more articles
Click on the topics below to browse the articles on this site. You can see more detail by clicking on the arrows. This highlights the location of the current
article: JDO identity models.
Related recent articles from Google News
Java on Google App Engine requires different approach SearchSOA "It's also true that you have to stick with JPA, JDO or plain SQL to store data." Most Java developers should at least be familiar with the Java Persistence ... and more » 9 Mar 2010 at 9:49am
Java EE 6 & GlassFish v3: Flexible, Extensible, and Simple CIOL For example, Java Persistence API 2.0 defines an API for the management of persistence and object/relational mapping. An RI is a binary distribution and is ... 8 Mar 2010 at 5:21am
Versant Releases Major Database Upgrade MarketWatch (press release) VOD 8 also offers various enhancements to JDO, the existing Java database standard, including upgrading the Versant JDO software development kit ... and more » 16 Feb 2010 at 8:11am
Developing a Master-Detail View SYS-CON Media (press release) This tutorial provides step-by-step instructions for creating a Web application that uses the Java Persistence API (JPA) version 2.0 with ... 24 Feb 2010 at 3:54pm
Objects, Abstraction, Data Structures and Design: Using Java version 5.0 by Elliot B. Koffman, Paul A. T. Wolfgang Average Customer Review: based on 5 reviews. Customer Review: A reader wrote that, "this book fails to address concurrency issues". But the books title never commits this. It's about teaching data-structures using Java (correctly). And it exactly does this with great success. Although I read it to refresh my knowledge, I enjoyed a lot as I learn the subject first time. It's CS for beginners, bu...
Object-oriented Data Structures Using Java by Nell B. Dale Average Customer Review: based on 6 reviews. Customer Review: This seller was very punctual with the shipping and delivery of the book and it was in very good condition like the ad had stipulated. I will recomment him to anyone ST
Data Structures and Other Objects Using Java (3rd Edition) by Michael Main Average Customer Review: based on 15 reviews. Customer Review: Even after taking a mid-level CS course where this book was the required text, this book still sits on my bookshelf at work for reference. Why? Well, certainly it is not the most comprehensive book of data structures in existence, nor is it written with a scholarly tone. But, that's the point! Michael Main's writing has the air of a...
Java Data Objects by David Jordan, Craig Russell Average Customer Review: based on 11 reviews. Customer Review: This book is definitely the best on java data objects! i have read the one from prentice hall and addison wesley`s. its true that the first code example doesnt work, what is a shame but if you overcome your frustration and have a look at the oreilly website you can fond the correct and again detailed information (and even reason) to...
Data Structures and Algorithms with Object-Oriented Design Patterns in Java (Worldwide Series in Computer Science) by Bruno R. Preiss Average Customer Review: based on 10 reviews. Customer Review: Hi, as an undergrad engineering student, I had this book for the coursebook in my algorithms course. Honestly speaking, it's good , very readable text. I never used any of the code examples fom the book in my assignments, yet they proved rather helpfull in understanding the material. Something, that I think is missing from this book...