Ah ok... There shouldn't work because it is pure SQL and NH only touch it to add the root alias and nothing more. For All: I would remember you that the mapping file has very few features regarding multi-RDBMS SQLs support. If I well remember there is only one place : database-object and its dialect-scope. The hbm file itself is a configuration file and you can use more than one sets of hbm for the same domain (I done it in my first NH application) for different RDBMS or even for different installation where the way you are mapping an entity graph may affect performance (that was my case). The session-factory configuration section allow you to define different sets of hbms (remember that you have a different session-factory configuration for each dialect). If you want maintain a big part of a mapping and change only a little part (as a 'formula' value) you can use XSLT or even more easy and *hbm-template, * substitute some special string by code, and configure NH to use the transformed hbm by code using one of the special "Add*" of the Configuration class.
2009/6/24 Stefan Nobis <[email protected]> > Fabio Maulo <[email protected]> writes: > > > the default_schema/default_catalog, of each mapping or of the > > session-factory-configuration does not work ? > > It does not work for the SQL in the 'formula' attribute of a property > (at least it didn't seem to work in 2.0.1GA last time I tried this). > > -- > Until the next mail..., > Stefan. > -- 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 -~----------~----~----~----~------~----~------~--~---
