× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



GENERATED BY DEFAULT

Instead of

GENERATED ALWAYS

Charles

On Thu, Feb 9, 2017 at 1:20 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

I have a set of SQL statements originally for MySQL (I think) which I am
attempting to convert to DB2.

These include things like this:

jobNumber INT NOT NULL AUTO_INCREMENT,

I believe that AUTO_INCREMENT needs to be replaced by GENERATED ALWAYS AS
IDENTITY but I also have existing data that has to be loaded into the table
and when I use this qualifier it refuses to allow data input for the
column. I tried removing the qualifier, inserting the data and then doing
an ALTER TABLE but it is not happy with that either.

So - question is - how do you do this in DB2 - it seems to work in Oracle,
SQL Server, MySQL, etc. so I'm guessing it can be done but I'm stumped.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.