Otis wrote:
miron wrote:
Otis wrote:
LITE version users don't get support, I'm sorry.
Lite limitations
LLBLGen Pro Lite is free, but is limited to 8 entities per project and comes with no support. If you want to create projects with more entities, please purchase a per-seat license. Code generated with the Lite version may be used for production purposes.
Though, we're not horrible people, so I'll give you a hint
-> the generated mapping files don't contain enough information for nhibernate to create the schema at runtime, e.g. we don't emit DB types into the mapping files. We don't do that because it will pollute the mapping files with info which isn't used normally. The designer offers a way to export create / update scripts from the model. You should use these scripts to create / update the schema of your DB, because they're created from the model itself.
I don't know why nhibernate chokes on [], as these characters are required to produce proper names in many situations (e.g. spaces in table names, other characters like '\' in table names etc.) perhaps you picked the wrong dialect?
- We want to buy full version. But before we would like all feature which we wish in this tool.
Then please download the trial version and request a trial license.
- Default types for columns is ok.
- When I remove character: '[' ']' e.g. [COLUMNA_NAME] SchemaUpdate work ok.
I have modified script to gen entities (this script is removing this characters.
But maybe there is better solution
Mirek
You can just export the create schema script and if you change the model, an update schema script:
http://www.llblgen.com/documentation/4.0/QuickStartGuides/mf_createscripts.htm
No, unfortunetly it is not best solution for us.
Update should be doing on users computer. And users can has different version of database schema.
I wrote about this issue on nhusers group. I got answer:
========================
Try using instead, like in table="
PERSON`" or better yet using the AutoQuote flag in the configuration.
Loquacious:
NHibernate.Cfg.Configuration cfg = new NHibernate.Cfg.Configuration()
.DataBaseIntegration(db =>
{
db.KeywordsAutoImport = Hbm2DDLKeyWords.AutoQuote;
///...
}
Or XML:
<hibernate-configuration xmlns="urn:nhibernate-configuration-2.2">
<session-factory>
<property name="hbm2ddl.keywords">auto-quote</property>
...
=========================
What is your proposition to solve this issue?
Using quota would be good but how to switch off adding [ ] in name of tables, columns, sequences (and maybe other database objects)?