[
https://issues.apache.org/jira/browse/SYNCOPE-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò closed SYNCOPE-1284.
-------------------------------------------
Resolution: Not A Problem
Glad to hear that you solved.
For future issues should you encounter, please discuss first in the user@
mailing list - see http://syncope.apache.org/mailing-lists.html
> Maven install for MSSQL using postgres-style DDL
> ------------------------------------------------
>
> Key: SYNCOPE-1284
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1284
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.7
> Environment: Windows 10 Enterprise, Apache Tomcat 8.5.27, Java 8, SQL
> Server 2014
> Reporter: Chuck Messenger
> Priority: Major
> Attachments: Master.properties, provisioning.properties
>
>
> Set up a new maven build of Syncope and made the documented changes to
> Master.properties and provisioning.properties, but DDL which executes on
> startup is erroring because the DDL being executed is Oracle or
> postgres-style DDL, not MSSQL. So there is either an undocumented change
> that needs to made to the configuration or something is broken. Piece of the
> stack trace:
> Caused by: <openjpa-2.4.2-r422266:1777108 nonfatal general error>
> org.apache.openjpa.persistence.PersistenceException: Column, parameter, or
> variable #2: Cannot find data type BLOB. \{stmnt 658558941 CREATE TABLE
> AccessToken (id VARCHAR(255) NOT NULL, authorities BLOB, body CLOB,
> expiryTime TIMESTAMP, owner VARCHAR(255), PRIMARY KEY (id))} [code=2715,
> state=S0006]
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:571)
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:467)
>
> This also happens with the DDL update script to the AccessToken table when
> trying to connect to an existing schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
