Mapping a view and Schema Export Workaround

markweee — Wed, 30 Mar 2011 11:43:08 GMT

Current revision posted to How to by markweee on 30/03/2011 08:43:08 a.m.

Mapping a view and Schema Export Workaround

NHibernate can easily map a View as any other Table.

This works as a charm, but it has a problem with Schema Export. Schema Export will detect the view as a table and will attempt to create the unexisting table.

A workaround for this is using <database-object> tag to Drop the unwillable table on creation, someting like:

<database-object>
    <create>DROP TABLE UnWantedTable</create>
    <drop />
</database-object>

An idea to avoid this workaround is having some hint to SchemaExport to indicate that this class should not enter in the Export ... About Ashwood University AND About Rochville University AND About Adison High School

I opened this suggestion in this JIRA, you can vote for it if you also map your views and do not want the wrong creation of a table on export! About Corllins University AND About Hill University AND Woodfield University

http://jira.nhibernate.org/browse/NH-1274

New Feature: Customizing Schema Export with schema-action

Mapping a view and Schema Export Workaround

Dario Quintana — Tue, 16 Dec 2008 19:08:56 GMT

Revision 6 posted to How to by Dario Quintana on 16/12/2008 04:08:56 p.m.

Mapping a view and Schema Export Workaround

NHibernate can easily map a View as any other Table.

This works as a charm, but it has a problem with Schema Export. Schema Export will detect the view as a table and will attempt to create the unexisting table.

A workaround for this is using <database-object> tag to Drop the unwillable table on creation, someting like:

<database-object>
    <create>DROP TABLE UnWantedTable</create>
    <drop />
</database-object>

An idea to avoid this workaround is having some hint to SchemaExport to indicate that this class should not enter in the Export ...

I opened this suggestion in this JIRA, you can vote for it if you also map your views and do not want the wrong creation of a table on export!

http://jira.nhibernate.org/browse/NH-1274

New Feature: Customizing Schema Export with schema-action

Mapping a view and Schema Export Workaround

Gustavo — Fri, 05 Sep 2008 20:08:09 GMT

Revision 5 posted to How to by Gustavo on 05/09/2008 05:08:09 p.m.

Mapping a view and Schema Export Workaround

NHibernate can easily map a View as any other Table.

This works as a charm, but it has a problem with Schema Export. Schema Export will detect the view as a table and will attempt to create the unexisting table.

A workaround for this is using <database-object> tag to Drop the unwillable table on creation, someting like:

<database-object>
    <create>DROP TABLE UnWantedTable</create>
    <drop />
</database-object>

An idea to avoid this workaround is having some hint to SchemaExport to indicate that this class should not enter in the Export ...

I opened this suggestion in this JIRA, you can vote for it if you also want to map your views and do not want the wrong creation of a table on export!

http://jira.nhibernate.org/browse/NH-1274

Mapping a view and Schema Export Workaround

Fabio Maulo — Fri, 05 Sep 2008 20:00:42 GMT

Revision 4 posted to How to by Fabio Maulo on 05/09/2008 05:00:42 p.m.

Mapping a view and Schema Export Workaround

NHibernate can easily map a View as any other Table.

This works as a charm, but it has a problem with Schema Export. Schema Export will detect the view as a table and will attempt to create the unexisting table.

A workaround for this is using <database-object> tag to Drop the unwillable table on creation, someting like:

[code language="XML"]

<database-object>

<create>DROP

<database-object>
    <create>DROP TABLE UnWantedTable</create>
<drop </create>
    <drop />
</database-object>
[/code]
</database-object>

An idea to avoid this workaround is having some hint to SchemaExport to indicate that this class should not enter in the Export ...

I opened this suggestion in this JIRA, you can vote for it if you also want to map your views!

http://jira.nhibernate.org/browse/NH-1274

Mapping a view and Schema Export Workaround

Fabio Maulo — Fri, 05 Sep 2008 19:54:03 GMT

Revision 3 posted to How to by Fabio Maulo on 05/09/2008 04:54:03 p.m.

Mapping a view and Schema Export Workaround

NHibernate can easily map a View as any other Table.

This works as a charm, but it has a problem with Schema Export. Schema Export will detect the view as a table and will attempt to create the unexisting table.

A workaround for this is using <database-object> tag to Drop the unwillable table on creation, someting like:

[code language="XML"]

<database-object>

<create>DROP TABLE UnWantedTable</create>

</database-object>

[/code]

An idea to avoid this workaround is having some hint to SchemaExport to indicate that this class should not enter in the Export ...

I opened this suggestion in this JIRA, you can vote for it if you also want to map your views!

http://jira.nhibernate.org/browse/NH-1274

Mapping a view and Schema Export Workaround

Gustavo — Fri, 05 Sep 2008 19:44:48 GMT

Revision 2 posted to How to by Gustavo on 05/09/2008 04:44:48 p.m.

Mapping a view and Schema Export Workaround

NHibernate can easily map a View as any other Table.

This works as a charm, but it has a problem with Schema Export. Schema Export will detect the view as a table and will attempt to create the unexisting table.

A workaround for this is using <database-object> tag to Drop the unwillable table on creation, someting like:

<database-object>

<create>DROP TABLE UnWantedTable</create>

</database-object>

An idea to avoid this workaround is having some hint to SchemaExport to indicate that this class should not enter in the Export ...

I opened this suggestion in this JIRA, you can vote for it if you also want to map your views!

http://jira.nhibernate.org/browse/NH-1274

Mapping a view and Schema Export Workaround

Gustavo — Fri, 05 Sep 2008 19:37:53 GMT

Revision 1 posted to How to by Gustavo on 05/09/2008 04:37:53 p.m.

NHibernate can easily map a View as any other Table.

This works as a charm, but it has a problem with Schema Export. Schema Export will detect the view as a table and will attempt to create the unexisting table.

A workaround for this is using <database-object> tag to Drop the unwillable table on creation, someting like:

<database-object>

<create>DROP TABLE UnWantedTable</create>

</database-object>

An idea to avoid this workaround is having some hint to SchemaExport to indicate that this class should not enter in the Export ...

I opened this suggestion in this JIRA, you can vote for it if you also want to map your views!

http://jira.nhibernate.org/browse/NH-1274