[Building Sakai] ENTITY_ Tables

Aaron Zeckoski azeckoski at unicon.net
Wed May 9 05:18:37 PDT 2012


They aren't used unless someone enables the entity properties storage
which is off by default.
Also, what index failure?
-AZ


On Wed, May 9, 2012 at 8:13 AM, Steve Swinsburg
<steve.swinsburg at gmail.com> wrote:
> I've never seen any data in those tables, possibly due to the index failure on certain MySQL versions, are they needed?
>
> Sent from my iPad
>
> On 09/05/2012, at 8:28 PM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>
>> Those are just the typical INFO level messages which you are free to
>> ignore (in essence, the DDL already ran and cannot run again because
>> the tables already exist).
>>
>> -AZ
>>
>>
>> On Wed, May 9, 2012 at 4:33 AM, David Horwitz <david.horwitz at uct.ac.za> wrote:
>>> Hi all
>>>
>>> on current trunk I'm seing this on the 2nd and subsequent startup:
>>>
>>> INFO Registered entity provider
>>> (org.sakaiproject.entitybroker.impl.entityprovider.EntityProviderManagerImpl$2)
>>> prefix (batch) with 1 capabilities
>>> INFO: [GenericDao] Could not execute first DDL line, skipping the rest:
>>> StatementCallback; bad SQL grammar [CREATE TABLE ENTITY_PROPERTIES (
>>> id            bigint(20) AUTO_INCREMENT NOT NULL PRIMARY KEY,
>>> entityRef       varchar(255) NOT NULL, entityPrefix    varchar(255) NOT
>>> NULL, propertyName    varchar(255) NOT NULL, propertyValue   text NOT
>>> NULL, INDEX (entityRef, entityPrefix, propertyName) )]; nested exception
>>> is com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
>>> 'ENTITY_PROPERTIES' already
>>> exists:com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
>>> 'ENTITY_PROPERTIES' already exists
>>> INFO: [GenericDao] Could not execute first DDL line, skipping the rest:
>>> StatementCallback; bad SQL grammar [CREATE TABLE ENTITY_TAG_APPLICATIONS
>>> ( id            bigint(20) AUTO_INCREMENT NOT NULL PRIMARY KEY,
>>> entityRef       varchar(255) NOT NULL, entityPrefix    varchar(255) NOT
>>> NULL, tag             varchar(255) NOT NULL, INDEX (entityRef,
>>> entityPrefix, tag) )]; nested exception is
>>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
>>> 'ENTITY_TAG_APPLICATIONS' already
>>> exists:com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
>>> 'ENTITY_TAG_APPLICATIONS' already exists
>>>
>>>
>>> The second and later restarts also fail. I'm not sure why
>>>
>>> D
>>>
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>
>>
>>
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile


More information about the sakai-dev mailing list