Re: [AgileWiki] a pressing matter--anyone interested in writing some commands?

[Bill La F. <Wil...@Su...>]

Ed,

Mmm, no. There is no JDBC. You can think of the database as an OODBMS, 
as long as you don't look too closely.

Actually, the objects aren't even Java objects. And the in-memory 
objects are simply data proxies with methods. And in-memory data isn't 
even stored in the data proxy objects, its stored in 
transactionally-aware caches.

Now here's the thing. The operations are easy, but some aspects of the 
API stink. I've been too busy getting things to work to focus to much on 
the clarity and usability of the API.

So, could your share your fresh view of the API? Lets go over some 
things together and see if we can't do some refactoring to add some clarity?

Or would it be more appropriate to discuss why I went with a whole new 
kind of database? Not that anyone really likes relational, but it is the 
industry standard, has been around a long time without anything better 
popping up, and a whole lot of folks know how to design systems around 
it! :-)

In any case, I appreciate your comment--everyone has been way too quiet 
for too long. And that's a terrible thing.

There's lots of contriversial things here. And I make a lot of wild 
claims. There should be pleanty to discuss!

Bill

Ed Tidwell wrote:

>Bill La Forge wrote:
>  
>
>>We need some commands then to create a descriptor unit,
>>to create a table descriptor unit and its columns table,
>>to create a row, and
>>to edit a row.
>>
>>Anyone interested?
>>
>>  
>>    
>>
>If I can use a POJO with simple CRUD (Create, Read, Update, Delete) JDBC 
>commands I've already got code for this.  ;-)
>Somehow I don't think this is what you had in mind though is it? 
>  
>