All Downloads are FREE. Search and download functionalities are using the official Maven repository.

org.jooq.CommentOnFinalStep Maven / Gradle / Ivy

There is a newer version: 3.19.15
Show newest version
/*
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 *
 * Other licenses:
 * -----------------------------------------------------------------------------
 * Commercial licenses for this work are available. These replace the above
 * ASL 2.0 and offer limited warranties, support, maintenance, and commercial
 * database integrations.
 *
 * For more information, please visit: http://www.jooq.org/licenses
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 */
package org.jooq;

import static org.jooq.SQLDialect.*;
import static org.jooq.impl.DSL.*;

import java.util.*;

import org.jooq.impl.DSL;

import org.jetbrains.annotations.*;

/**
 * A step in the construction of the COMMENT ON TABLE statement.
 * 

*

Referencing XYZ*Step types directly from client code

*

* It is usually not recommended to reference any XYZ*Step types * directly from client code, or assign them to local variables. When writing * dynamic SQL, creating a statement's components dynamically, and passing them * to the DSL API statically is usually a better choice. See the manual's * section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. *

* Drawbacks of referencing the XYZ*Step types directly: *

    *
  • They're operating on mutable implementations (as of jOOQ 3.x)
  • *
  • They're less composable and not easy to get right when dynamic SQL gets * complex
  • *
  • They're less readable
  • *
  • They might have binary incompatible changes between minor releases
  • *
*

* @deprecated - [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly */ @SuppressWarnings({ "unused" }) @Deprecated(forRemoval = true, since = "3.15") public interface CommentOnFinalStep extends DDLQuery { }





© 2015 - 2024 Weber Informatics LLC | Privacy Policy