[baseten-users] Problems with baseten 1.6.2

[Jianhua Meng]

Hi Tuukka,


Since I moved to 1.6.2, I have run into a significant problem. Our  
code base worked fine prior to the move. I'm using the official  
release from your site, i.e. BaseTen-1.6.2.dmg.  I tried the trunk  
first and had to abandon the idea due to stability issues.

After I imported our model with BaseTenAssistant, everything appears  
to be normal in the sense that BaseTenAssistant installs the  
application schema and baseten schema. When I ran our app, a problem  
surfaced: the app fails to create objects involving relationships. I  
stepped through our code and found out that the code breaks at point  
where it attempts to access a relationship that is supposed to exist  
according to the model. According the  
EntityDescription.relationshipsByName, no relationships are defined.  
This unexpected discovery led me to poke around in the baseten schema.  
To my surprise, the table 'baseten.relationship' is empty. My common  
sense tells me something may be wrong here.  I expected to see  
hundreds of rows in this table (from my experience with a prior  
release).  I admit I don't understand the architecture of baseten  
schema, I'm just pointing out the obvious discrepancy. This may or may  
not be related to the problem I'm facing. Please advise on what is  
going on.

Other observations:
+ the baseten schema has changed relative to what I saw before we  
moved to 1.6.2
+ deploying a baseten based application is a lot harder now since we  
cannot rely on a simple dump and load. baseten schema now has a  
dependency on the physical object ids of the application objects. We  
have been trying to devise a work around, we haven't found a robust  
and satisfactory solution yet. You suggested some workarounds a while  
ago, they are rather awkward.  It would be nice if the baseten  
framework includes some high level api for applications to: (1)  
install baseten schema; (2) reinstall baseten schema; (3) report if  
baseten schema needs to be reinstalled.


Thanks for your help.

Regards,
Jianhua Meng
QuickCeph Systems