Exception changing status error

Rennur

I'm dead in the water,

Got is error out of nowhere. Just tried to put the version into test.

The system didn't create this field (yes/no attribute) in the MySQL database for some reason. Once I created the database field manually, I got this error:
(note the column name is different)

Can't put the version operational.

Stuck. Help please.

Cheers

Rennur

By the way, there is not duplicate column name 'Name' as error #2 suggests.

Rennur

Well I deleted that YES/NO attribute but I still get error #2.

Rennur

Does anyone know where is the stored procedure that AwareIM keeps trying to execute? Eg. altering the column.

Rennur

I imported that BSV into a new Business Space and go a message to run CTRL-I.

I went back to the original B'Space that was giving me the error & did CTRL-I. I found and fixed duplicate IDs but afterwards I get the the same error again.

WTF is going on?

A YES/NO attribute is trying to alter the column to type Name MEDIUMTEXT (Name is an plain text attribute by the way and not a type) unknown column in BO.

I have experienced this once before and to fix it I had to basically dump all SQL data, delete business space and re-do re import BSV & data from scratch.

I haven't done anything strange but simply create 3 attributes in a BO for this to happen.

Rennur

Again today, I created a plain text attribute 'Title', then changed the name to 'Subject' and now I'm getting this error:

Server encountered an exception Error altering column Subject for table BASTESTDOMAINCR_NOTE to type Note MEDIUMTEXT Unknown column 'Subject' in 'bastestdomaincr_note'

Aware never created the database field in the first place.
So I create it manually & get this error:

Server encountered an exception Error altering column Subject for table BASTESTDOMAINCR_NOTE to type Note MEDIUMTEXT Duplicate column name 'Note'

There is no duplicate column 'Note'.
Subject column and Note column are 2 different things, the error altering column Subject to type Note (??) MEDIUMTEXT Duplicate column name 'Note'
Are there issues in the way AwareIM treats 'mediumtext' attributes??

So frigging annoying. :evil:

Rennur

I delete the Subject field in the database and I delete the Subject attribute but the error persists.

Server encountered an exception Error altering column Subject for table BASTESTDOMAINCR_NOTE to type Note MEDIUMTEXT Unknown column 'Subject' in 'bastestdomaincr_note'

Does AwareIM have a stored procedure within the BSV than keeps trying to execute this?

Rennur

Again, on another BO, I've deleted 2 attributes I don't need via Config Tool and when I try to put the version under test I get:

Server encountered an exception Error dropping columns for table BASTESTDOMAINCR_myBO Can't DROP 'myAttribute'; check that column/key exists

I'm finding version 5.8 too buggy to develop with, hopefully all the bug will be squashed in 5.9.

Rennur

Phew, luckily the Config tool has the undo button, which undeleted the attributes and I was able to put the version under test.

Rennur

There is browser error now.

Unable to find MyBO.Date in aggregate operation SUM
com.bas.basserver.executionengine.ExecutionException: Internal error. Error persisting business object MyBO Unknown column 'myAttr_PDF_DOCDATA' in 'field list'

The database field exists, I'm dumbfounded as to what is causing this.

Powerm

Seems you have messed-up the bsv version and the database table versions.
Best thing is to export the bsv and start with a clean database.

kklosson

I have to agree. I have been in similar situations and I've even had times when database restoration couldn't get me out of it. This is perhaps AwareIM's Achilles Heel. For all that AwareIM does, the configurator can get into a jam with the basdbtest database and there may be times when you have to purge it altogether. After working with AwareIM for a few years now, I am committed to avoiding this. Here are my personal working tips:

Work and publish in the smallest publishable increments.
Make a backup of the basdbtest database before each session, or at least before any session in which business objects are manipulated.
If possible, and for all new installations, set your initial business space to a template BSV, like CRM. This will make things a bit easier if you have to purge your test database.
Be particularly cautious when manipulating business objects and relationships. It's not that this is a flaw in AwareIM, it's that AwareIM's ability to abstract the developer from the database is awesome and powerful. With great power comes great responsibility.

I would be much in favor of a concept within AwareIM to snapshot the BSV and database versions for a coordinated roll-back, though this can be done well enough by the developer.