Use the UNIQUEKEY(table_name) function. For example, INSERT INTO MyTable ( my_unique_id, my_value ) VALUES ( UNIQUEKEY('MyTable'), 'record value' ) With a clever use of the DEFAULT clause when creating a table you can make it automatic. eg. CREATE TABLE MyTable ( my_unique_id NUMERIC DEFAULT UNIQUEKEY('MyTable'), my_value LONGVARCHAR(1000) ) The UNIQUEKEY function is an atomic operation that will return a set of sequential numbers for a table on a first serve basis.

Since RACE supports multiple queries in a database tag, you can insert the line of data, then select the last auto_increment ID back from the database: lt;database name="dbfoo" query="INSERT INTO foo (auto,text) VALUES(NULL,'text'); SELECT LAST_INSERT_ID() as LASTID from foo">

The most common cause is the use of double-quotes around table or column names during table creation. When double-quotes are used, table and column names (called identifiers) are stored case-sensitive, meaning you must use double-quotes when referencing the names in a query. Some interfaces, like pgAdmin, automatically double-quote identifiers during table creation. So, for identifiers to be recognized, you must either:

A collection of 19 FAQs on working with database objects in PL/SQL. Clear answers are provided with tutorial exercises on defining, opening, and closing cursors, looping through cursors, defining and using cursor variables.

header 1 || | || header 2 || | || header 2 || *----------------+----------------*--------------------------+ cell1 | cell1 | cell3 *----------------+----------------*--------------------------+

We do not support ALTER TABLE DROP COLUMN, but do this: SELECT ... -- select all columns but the one you want to remove INTO TABLE new_table FROM old_table; DROP TABLE old_table; ALTER TABLE new_table RENAME TO old_table;

In User and Role, SQLRelatedJoin is used with createRelatedTable=False so the intermediate table is not created automatically. We also set the intermediate table name with intermediateTable='user_roles'. UserRoles is the definition of our intermediate table. UserRoles creates a unique index to make sure we don't have duplicate data in the database. We also added an extra field called active which has a boolean value.

Many RDBMS allow IDENTITY and auto-increment columns to be overwritten with client values implicitly. DbUnit can be used with these RDBMS natively. Some databases, like MS SQL Server and Sybase, need to explicitly activate client values writing. The way to activate this feature is vendor specific.

The most common cause of recognized names is the use of double-quotes around table or column names during table creation. When double-quotes are used, table and column names (called identifiers) are stored case-sensitive, meaning you must use double-quotes when referencing the names in a query. Some interfaces, like pgAdmin, automatically double-quote identifiers during table creation. So, for identifiers to be recognized, you must either:

We're looking for he most efficient way to apply our database releases to dozens of Oracle instances on the same day.

To delete a row or column from your place your cursor to the cell of the row or column you want to delete and click the “Delete Rows” or “Delete Columns” button on your Page Editor tool bar respectively. You can also place your cursor to the cell of the row or column you want to delete and right click and select the “Delete Rows” or “Delete Columns” from the menu.

increment is the amount of money that you choose is needed to outbid somebody, or the starting bid. For example, if a starting bid is $20.00, with $1.00 increments, the lowest possible next bid could be $21.00. It's good to keep increments low, like $1.00 in the example, for maximum bidding. This is due to the "it's only a dollar more" effect. Unless, of course, your auctioning something expensive, then you should raise the increment to $2.00, $3.00, $4.00, and so on.

DataTable myTable = new DataTable("Customers"); ... DataColumn cCustID = new DataColumn("CustID", typeof(int)); cCustID.AutoIncrement = true; cCustID.AutoIncrementSeed = 1; cCustID.AutoIncrementStep = 1; myTable.Columns.Add(cCustID...

Propel supports only native id generation. That means that for MySQL Propel will use AUTO_INCREMENT, IDENTITY() for MS SQL Server, CREATE SEQUENCE ... for PostgreSQL, etc.

Use p{dimen} as the column specification. That wraps them to that width specified by dimen. Example: \begin{tabular}{|l|l|r|p{2in}|}

The Bid Increment raises the bidding each time by that minimum amount (you can always bump it up even higher or enter a Proxy Bid, in which case the system will bid either the bid increment or enough of your stated amount to make you the leading bidder. The purpose of the bid increment is to keep someone from outbidding you by some silly amount like $.01. It protects you and assures the seller of getting a decent return if the item is hotly contested.

Create a generator and a trigger to associate it with the field. The following example creates a generator named PROD_ID_GEN, and a trigger for table ORDERS which uses the generator to perform auto increment on field PRODUCE_ID with increment size of 1. $dbh->do("CREATE GENERATOR PROD_ID_GEN"); $dbh->do( "CREATE TRIGGER INC_PROD_ID FOR ORDERS BEFORE INSERT POSITION 0 AS BEGIN NEW.PRODUCE_ID = GEN_ID(PROD_ID_GEN, 1); END");

Add the column in the database. This can be down using the ALTER command in sql, or by using a GUI provided by the creaters of your database. Locate the JBean class for the table. For example, if you are adding a column to the Specimens table, the class would be SpecimenBean. Locate the array of TFields given by the getFieldsArray() method. You will need to add the name of the column and type of the column to this array.