Improving schema DDL there is some DDL that (Web site counters)
Improving schema DDL there is some DDL that Hibernate can t create automatically. This includes all kinds of highly vendor-specific performance options and any other DDL that is relevant only for the physical storage of data (tablespaces, for example). One reason this kind of DDL has no mapping elements or annotations is that there are too many variations and possibilities nobody can or wants to maintain more than 25 database dialects with all the possible combinations of DDL. A second, much more important reason, is that you should always ask your DBA to finalize your database schema. For example, did you know that indexes on foreign key columns can hurt performance in some situations and therefore aren t automatically generated by Hibernate? We recommend that DBAs get involved early and verify the automatically generated DDL from Hibernate. A common process, if you re starting with a new application and new database, is to generate DDL with Hibernate automatically during development; database performance concerns shouldn t and usually don t play an important role at that stage. At the same time (or later, during testing), a professional DBA verifies and optimizes the SQL DDL and creates the final database schema. You can export the DDL into a text file and hand it to your DBA. Or and this is the option you ve seen a few times already you can add customized DDL statements to your mapping metadata:
We recommend you use shared web hosting services, because many users agree that it is cheap, reliable and customer-satisfying webhost.