This company started when we were all at Universisty, which ment that we did not have enoguh time to code, or if we did, it was time we were getting from or social life or from the time we should expend doing universisty work.
Now everything is completely different, we have the time, and ofcourse the energy to work. Currently we are moving fast although not as fast as I would like. We have divided the work accordingly to what we know and I believe it shoudl work quite well.
This weekend I’m going to expend it modifying the database library we have to far to be able to interact with tables that were created through other means. So far, our library assumed (when you ass you make and ass of me and you, I know…) that the developer would just want to be able to related his objects with tables that were generated by the library, but this ofcourse was WRONG.
My attempt is to allow a developer tell that a property of a .Net object is a foreign key of a previously existing table. At the same time I want to add the idea of weak objects (or tables, in this case we use them the same way). When we add a weak object to the database this will only exist while it has a relation with an other IPersistentObject. This is a very interesting problem since I have to keep track of the relation from other objects to the weak object rather than the other way around. This approach will allow to create weak object that will be deleted when ever they are not needed any more, making the DB alot cleaner.
I’ll be updating about how the development is going during the weekend, but look promising and “fun”
