Does nhibernate use the unique-key clause for anything else than
creating unique keys when in schemaexport?

Francisco A. Lozano



On Mon, Sep 28, 2009 at 14:25, Fabio Maulo <[email protected]> wrote:
> UK in the mapping is to create UKĀ grouping properties and not to give a name
> to UK.
> If you need some RDBMS specific feature theĀ <database-object>, specifying
> the dialect-scope, is the way.
>
> 2009/9/28 Francisco A. Lozano <[email protected]>
>>
>> I thought about that... but the name generated for the AK is not what
>> I've put in the unique-key attribute, it's something like
>> "UQ__region__90C6EECD443605EA", which I don't think it's safe to
>> reference in my mappings, as it's probably subject to change...
>>
>> It would be great to be able to apply a naming scheme class to the
>> schema-export objects.
>>
>> Francisco A. Lozano
>>
>>
>> On Mon, Sep 28, 2009 at 12:51, Roger Kratz <[email protected]>
>> wrote:
>> >
>> > You could alter the pk using <database-object>.
>> >
>> > (AFAIK - if the functionality hasn't been added recently, you can't do
>> > it in the class mappings)
>> >
>> > -----Original Message-----
>> > From: [email protected] [mailto:[email protected]] On
>> > Behalf Of Francisco A. Lozano
>> > Sent: den 28 september 2009 12:16
>> > To: [email protected]
>> > Subject: [nhusers] Clustered index from SchemaExport?
>> >
>> >
>> > Hi,
>> >
>> > I'm using SQL Server and SchemaExport to automatically generate my
>> > database schema. Is there any way to tell SchemaExport that I want a
>> > given unique-key's index clustered?
>> >
>> > Francisco A. Lozano
>> >
>> >
>> >
>> >
>> > >
>>
>>
>
>
>
> --
> Fabio Maulo
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to