Spring Framework
  1. Spring Framework
  2. SPR-6836

HibernateJpaVendorAdapter sets hibernate.hbm2ddl.auto to "update"

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.5.6
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Last commented by a User:
      false

      Description

      When HibernateJpaVendorAdapter is configured with generateDdl="true" the value of hibernate.hbm2ddl.auto is set to "update", overriding actual value specified in persistence.xml.

        Activity

        Hide
        Juergen Hoeller added a comment -

        Well, that's the point of the "generateDdl" flag: It will set the corresponding property of the underlying persistence provider. If you'd rather configure those properties natively (e.g. in persistence.xml), then simply don't bother with setting "generateDdl" on the JpaVendorAdapter...

        Juergen

        Show
        Juergen Hoeller added a comment - Well, that's the point of the "generateDdl" flag: It will set the corresponding property of the underlying persistence provider. If you'd rather configure those properties natively (e.g. in persistence.xml), then simply don't bother with setting "generateDdl" on the JpaVendorAdapter... Juergen
        Hide
        Ivan Balashov added a comment -

        This flag is rather misleading for Hibernate, which beside "update" also has "create" and "create-drop" options.

        To enable "create", generateDdl should be set to "false", which at the first sight doesn't make any sense.

        Show
        Ivan Balashov added a comment - This flag is rather misleading for Hibernate, which beside "update" also has "create" and "create-drop" options. To enable "create", generateDdl should be set to "false", which at the first sight doesn't make any sense.
        Hide
        Rossen Stoyanchev added a comment -

        This issue has been resolved through a selective bulk update, as part of a larger effort to better manage unresolved issues. To qualify for the update, the issue was either created before Spring 3.0 or affects a version older than Spring 3.0 and is not a bug.

        There is a good chance the request was made obsolete, or at least partly outdated, by changes in later versions of Spring including deprecations. It is also possible it didn't get enough traction or we didn't have enough time to address it. One way or another, we didn't get to it.

        If you believe the issue, or some aspects of it, are still relevant and worth pursuing at present you may re-open this issue or create a new one with a more up-to-date description.

        We thank you for your contributions and encourage you to become familiar with the current process of managing Spring Framework JIRA issues that has been in use for over a year.

        Show
        Rossen Stoyanchev added a comment - This issue has been resolved through a selective bulk update, as part of a larger effort to better manage unresolved issues. To qualify for the update, the issue was either created before Spring 3.0 or affects a version older than Spring 3.0 and is not a bug. There is a good chance the request was made obsolete, or at least partly outdated, by changes in later versions of Spring including deprecations. It is also possible it didn't get enough traction or we didn't have enough time to address it. One way or another, we didn't get to it. If you believe the issue, or some aspects of it, are still relevant and worth pursuing at present you may re-open this issue or create a new one with a more up-to-date description. We thank you for your contributions and encourage you to become familiar with the current process of managing Spring Framework JIRA issues that has been in use for over a year.

          People

          • Assignee:
            Juergen Hoeller
            Reporter:
            Ivan Balashov
            Last updater:
            Trevor Marshall
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since last comment:
              1 year, 44 weeks, 2 days ago