Yes the tables were auto created and it is an identity column.
SQL create table script from SQL manager:
CREATE TABLE [dbo].[RegisteredServiceImpl](
[id] [numeric](19, 0) IDENTITY(1,1) NOT NULL,
[description] [varchar](255) NULL,
[serviceId] [varchar](255) NULL,
[name] [varchar](255) NULL,
[theme] [varchar](255) NULL,
[allowedToProxy] [tinyint] NOT NULL,
[enabled] [tinyint] NOT NULL,
[ssoEnabled] [tinyint] NOT NULL,
[anonymousAccess] [tinyint] NOT NULL,
[ignoreAttributes] [tinyint] NOT NULL,
[evaluation_order] [int] NOT NULL,
PRIMARY KEY CLUSTERED
(
[id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
A
On Jan 11, 2010, at 7:31 PM, Marvin Addison wrote:
> Your entity manager factory definition looks good for SQL Server.
> Were your tables auto-created by Hibernate? (This is what Hibernate
> does by default if the table is not found.) Can you confirm that the
> id column is in fact an identity column in the database? I have the
> infrastructure to try to reproduce, but I'd like to rule out
> configuration problems beforehand.
>
> M
>
> --
> You are currently subscribed to [email protected] as:
> [email protected]
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
