tag:blogger.com,1999:blog-317307232011-11-27T19:44:17.205-06:00This site contains ideas on the next generation of database technology. AOP is a compeling software development paradigm. This new technology will affect database management, the systems, and representions of data. Here we will discuss these changes.mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.comBlogger151100tag:blogger.com,1999:blog-31730723.post-39878216904910152062010-11-05T20:54:00.003-05:002010-11-05T21:12:21.632-05:00

I have a problem, sometimes I think too much, but I don't ever accuse you of thinking too much or "over"engineering or "thinking" too early. But, I have been wondering about these new ways software is recommended to be developed. This installment of this series will analyze the consequences of the use of the term "grow" as applied to creating software.The reason a certain term is chosen must be

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-62818988177583707812009-10-06T21:43:00.014-05:002009-10-07T23:15:49.328-05:00

Don't you wish sometimes that Java had the feature for exceptions to automatically capture the values of the variables in the context that were present when an exception occurs? Well I guess we just have to do it manually. Let's see what it would look like:public class SomeClass {public void someMethod(String x) { try { int pos = x.indexOf("abc"); String y = x.susstring(pos); } catch (

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-72662213788655003522009-03-11T22:49:00.003-05:002009-03-12T22:49:54.960-05:00

The beauty of object oriented programming is that you can have a program that resembles the real world objects that it is to represent. Domain driven design is the notion that you create models based on a "domain". That is a subject area. This can be fuzzy, or it can be industry agreed upon. The catch is that you are writing an application, and not a domain model. What does that mean? It

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-16196428056094255112009-03-09T12:25:00.009-05:002009-03-10T23:25:43.791-05:00

Suppose you want to keep your POJO really a POJO? If you use JPA annotations on a class, is it still really a POJO? A POJO should be usable as a domain object independent of whether it came from a database, or from a remote service. So If I see @Entity on your POJO, I know it is really a database object, and I start thinking all about it's dependencies, do I need a transaction, do I need a

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-47268456205115807612008-08-25T23:08:00.002-05:002008-08-25T23:13:00.368-05:00

some textpublic class MyClass { private String myfield;}

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-73706041681123592402007-12-05T21:24:00.000-06:002007-12-05T21:47:08.211-06:00

When you are designing a domain model using JPA or hibernate or another declarative approach to ORM, you must decide the cascade rules for creating and deletign objects that are related to each other. When you have a one-to-many relationship between two objects, when an object is persisted, you need to decide if the related object should be automatically persisted as well, or should you have to

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com3tag:blogger.com,1999:blog-31730723.post-60665448139042044692007-08-05T22:04:00.000-05:002007-08-05T22:21:51.858-05:00

When you model your system in object oriented methodologies, you have to choose whether a class "is-a" a certain type or if it "has-a" a certain type. Is this confusing? The best way to think of this is to ask what is a customer? If you have a class "Person" in your model, then you might think that a "Customer" is-a "Person". But that starts to get complicated. A customer is someone who has

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-82906600390717629992007-05-22T12:32:00.000-05:002007-12-05T21:37:42.319-06:00

Introduction to Aspect Query Language In this document we will discuss a new query language called "aspect query language" which allows you to write queries against Transcendental Beans, the aspect oriented database. AQL is similar to other query languages in that it starts with a familiar select style syntax. It has results and condition where clauses. The results from an

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-32493234768608184242007-03-19T12:29:00.000-05:002007-12-05T21:37:42.331-06:00

Technical White Paper Application Architecture using a Native Aspect Oriented Database Level: Intermediate March 16, 2007 Version 1.0 Abstract: The architecture of an application is chosen to enable the development of the software that achieve the goals of the business at hand. Many times an architecture is chosen from a pattern or template of common architectures such as MVC or SOA

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-54089966761146099292007-02-28T22:18:00.000-06:002007-02-28T22:43:33.566-06:00

If a database has persistent data that comes from an aspect, what would it be? Examples of this would be design patterns implemented as an aspect, metadata about an object, or other data that is introduced by the aspect. Also, a data "feature" will change the way data is stored in the database. The feature of a "revision history" is implemented as an aspect of the persistent data. The feature

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-39640700533319343952007-02-28T06:16:00.000-06:002007-02-28T06:27:30.274-06:00

An aspect oriented database should support an aspect oriented query language. What would the aspect paradigm do to influence other query languages? There is SQL, JDOQL, EJBQL, OQL, and others. AQL or "Aspect Query Language" would be a query language that supports queries against an aspect oriented database. There are persistent aspects, and persistent data that has been annotated by aspect

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com1tag:blogger.com,1999:blog-31730723.post-14128391927125063592007-01-07T13:26:00.000-06:002007-02-28T00:09:49.373-06:00

The real world if full of context that introduces meaning into our data. DBMS systems can benefit from the management of these contexts and a representional approach to defining what the meaning related contexts are.What is a relationship? There are two parties, and a rolle that describes the relationship. So a customer could be related to an address with the roll of billing address. But the

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-1160363960451879032006-10-08T22:14:00.000-05:002006-10-31T22:43:06.633-06:00

An aspect oriented database is an object oriented database that supports the concepts of aspect orientation. An object oriented database is a relational database that supports the cpncepts of object orientation. So everyone knows what an RDBMS is? A tabular approach to defining data that is to be persisted or stored for long term storage and retrieval. Tables can be related to each other by

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-1155407283969294232006-08-12T13:23:00.000-05:002006-10-31T22:43:06.554-06:00

What is a database? A place to store information that can retrieve that information at a later time. An RDBMS is the most popular form of "database". But a bunch of tables isn't an intuitive way to represent information. We are taught that it is, but is this really true?Did you ever think that putting time modified information along with customer name, and other customer data was wrong? I

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0tag:blogger.com,1999:blog-31730723.post-1153968577408718152006-07-26T21:45:00.000-05:002006-10-31T22:43:06.474-06:00

I will be bringing my ideas on a new way to manage database data. Why should AI systems be the only place where sophisticated representations of data exist? The trend towards AOP is inevitable. Aspect Oriented Database Management will bring a new world of possibilities to applications and the industry of domain models.

mikehttp://www.blogger.com/profile/10513845445987963053noreply@blogger.com0