3.0.0 RC

Mmmhhh... I can't understand how this may happen: I don't have any code that old.

I had done a tar.gz of the previous version (2.6.3). If I untar it in place, I get the same type of error!

tail projector_20121118.log
2012-11-18 16:40:37 ***** ERROR ***** Strack trace :
2012-11-18 16:40:37 ***** ERROR ***** #0 Sql->query called at [/opt/projectorria/model/persistence/SqlElement.php:1103]
2012-11-18 16:40:37 ***** ERROR ***** #1 SqlElement->getSqlElementsFromCriteria called at [/opt/projectorria/tool/loginCheck.php:30]
2012-11-18 16:40:37 ===== TRACE ===== Login error for user 'bernard'
2012-11-18 16:40:37 ***** ERROR ***** Exception-[42S02] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'projectorria.user' doesn't exist
2012-11-18 16:40:37 ***** ERROR ***** For query : select * from user where user.name ='bernard' and user.isUser = '1'
2012-11-18 16:40:37 ***** ERROR ***** Strack trace :
2012-11-18 16:40:37 ***** ERROR ***** #0 Sql->query called at [/opt/projectorria/model/persistence/SqlElement.php:1103]
2012-11-18 16:40:37 ***** ERROR ***** #1 SqlElement->getSqlElementsFromCriteria called at [/opt/projectorria/tool/loginCheck.php:30]
2012-11-18 16:40:37 ===== TRACE ===== Login error for user 'bernard'

What can I do?

Well, I think I begin to understand: The upgrade of table must hav begun but never properly ended and I'm stucked with a new base structure and a code which 'think' it hasn't been done.
I _must_ tweak to find out where... Can you help me?

I finally found out a workaround but it does not satisfy me: I had to rename the resource table into user, then give a _full write access_ to the entire directory tree to have the migration done.

It's a *serious security hole* to have to do that. I wouldn't never have to do that. I admit the product has to write logs and reports but if he can't write to a specific file during the migration, I have to be notified and the migration has to be rollbacked or a new run must go straightforward.