[baseten-users] Plans for PITA Integration

[Ben Einstein]

Hi Tuukka,

Sorry, I left out a field! There's also a "pitaPrimaryKey" field in  
all the tables that holds the reference to the current/original  
record. As of now, the format for that column is dynamically pulled  
from the existing primary key in the DB. In the databases I've worked  
on before, there's usually just a single primary key, but I'm starting  
to worry that could be an issue here? Maybe we should discuss the  
design a bit more? Is that appropriate for this mailing list?

Ben

On Jun 9, 2009, at 7:56 PM, Tuukka Norri wrote:

> Ben Einstein kirjoitti 9.6.2009 kello 13.05:
>> 4. Each PITA-enabled table has 6 extra fields: startedOn,  
>> startedBy, startedReason, endedOn, endedBy, endedReason.
>
> Hi!
> I remember reading about a PTA system like this but can't remember  
> the details right now. How are primary keys handled? If startedOn  
> and endedOn are part of them, making foreign keys could become  
> somewhat painful. On the other hand, if they're not, there should  
> probably be a means to update currently referencing records.  
> Inserting a copy of the current record into tables that have  
> referencing foreign keys comes to mind.
> -- 
> Best regards,
> Tuukka Norri
> MK&C
>
>
> _______________________________________________
> baseten-users mailing list
> baseten-users at lists.basetenframework.org
> http://lists.basetenframework.org/mailman/listinfo/baseten-users