ER_DUP_WINDOW_NAME

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 4010

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0 as error number 4010

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 4010

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0 as error number 4010

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 4010

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0 as error number 4010

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1 as error number 4010

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0 as error number 4010

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1 as error number 4010

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0 as error number 4001

  • Error number changed in MariaDB Community Server 10.2.1 from 4001 to 4007

  • Error number changed in MariaDB Community Server 10.2.2 from 4007 to 4010

Release Series

History

10.6 Enterprise

  • Present starting in MariaDB Enterprise Server 10.6.4-1 as error number 4010

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1 as error number 4010

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1 as error number 4010