SQL does not support keyed tables.
When doing a reverse engineering, unique keys can be converted into a
primary key. Non unique keys are not supported.
... but I'd not waste my primary key for a compound key.
Before converting the physical file I'd suggest to create a new logical file
(or better an SQL index) with the key fields of the physical file ... and
then replace the physical file in all programs with keyed access (native
I/O) with the new logical file or SQL index. After you can easily convert.
Another approach would generating the SQL table with a new name, then create
a logical file (or better an SQL Index) with the same name of the former
physical file.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
Modernization ? Education ? Consulting on IBM i
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of gio.cot
via RPG400-L
Sent: Samstag, 10. Dezember 2022 17:02
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Cc: gio.cot <gio.cot@xxxxxxxxxxx>
Subject: SQL Create Or Replace with keyed Fiile
Hi all
I have a phisical file with two key fields created from DDS for compile my
RPG program; this file is then duplicated with CRTDUPOBJ to Qtemp and then
via "SQL Create or Replace", populated with records/rows, but in this way
(SQL Create or Replace) i lost the key fields; the file became a nokeyed
file !!
Crtdupobj
create or Replace table qtemp.oc32W AS (
WITH pr AS ( bla , bla , bla )
with data
ON REPLACE DELETE ROWS
Is there any way to avoid it (lost key fields ??)
Thanks in advance
Gio
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
