Ticket #205 (new enhancement)

Opened 9 months ago

Last modified 9 months ago

Point In Time Architecture Implementation

Reported by: beinstein Owned by: tsnorri
Priority: major Milestone: Distant future
Component: BaseTen Keywords:
Cc:

Description

I'm on the brink of switching one of our big enterprise applications over to BaseTen? from MySQL. One of the most important features necessary for us to commit to the switch is full compatibility with a Point in Time Architecture. Because BaseTen?'s high-level public methods don't easily facilitate these changes, it would be necessary to change some of the internal methods. I was wondering if you think this may be a useful feature for other BaseTen? users, and if so, should those changes be integrated into the trunk or hosted separately? I can provide more detail on how a PITA system works, if necessary.

Change History

Changed 9 months ago by tsnorri

  • milestone deleted

Hi!

One of our own applications uses both BaseTen and a point-in-time-architecture. Our implementation made each object represent a change in the database. Please do post your requirements to the mailing list at baseten-users@…, though. In my opinion, this kind of an enhancement sounds quite useful to everyone.

Changed 9 months ago by tsnorri

  • milestone set to Distant future

Changed 9 months ago by beinstein

Sounds great. I think this kind of enhancement could be a big attractor to many prospective BX users. I've currently fully implemented the system for the assistant, and will hopefully find some time soon to start integrating it into the framework. I'm glad this kind of interest exists. What's the process to commit to the project?

Note: See TracTickets for help on using tickets.