[baseten-users] Problems with release 1.6

[Jianhua Meng]

Hi List,

I thought I'd document some problems we experienced after moving to  
1.6 recently in the hope that someone might shed some light on them.

The problem:
We have been using a simple deployment process for installing baseten  
based apps on desired target machines without trouble until 1.6. The  
process consists of dumping the seed database which I use for  
development and use the dump to load any desired target computer for  
testing.  The problem appears to be that on any target computer after  
the loading the database from the dump, the app gets stuck from an  
exception caused by 'Entity ... doesn't have relationship  
capability'.  I checked with BaseTenAssistant and confirmed that all  
the entities are indeed not enabled, to my surprise. I ran the same  
check against my seed database, all the entities are enabled as  
expected.

Investigation:
I poked around some of the baseten tables. I noticed  
baseten.enabled_relation and baseten.primary_key. On both my seed  
database and the test database, the tables contain identical  
information (which tells me the dump/load works fine). It is puzzling  
that the app works fine against the seed database on my machine but  
does not work against the test database on another machine. I don't  
understand why BaseTenAssistant would report differently regarding  
enabled relations when the underlying data is identical. How does  
BaseTenAssistant tell if a table is enabled?

Any insight on the problem will be greatly appreciated.

Regards,
Jianhua Meng
QuickCeph Systems, Inc