× 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.


  1.  Home
  2. MIDRANGE-L
  3. October 2010

Re: SQL database object names longer than 10 charactersand mixed case?

... I would be carefull to change my paradigm from *SYS to *SQL. There are some AS/400 considerations to have in mind, as:
- having the database objects spread over multiple libraries
- using external stored procedures
- having stored procedures using external rpg programs
- using ovrdbf, share yes
- using SQL and native database access in conjunction
Starting a new project or in a phase of redesign, I would recommend to go the SQL mainstream road, using naming *SQL, no record level access and DDS (for database creation), one database for my datamodel, using referential constraints, using a complete view layer instead of using the tables, no functional business rules in the database, fully normalization of datamodell...

Dieter Bender

--------------------------------------------------
From: "Neill Harper" <neill.harper@xxxxxxxx>
Sent: Saturday, October 30, 2010 9:51 PM
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Subject: RE: SQL database object names longer than 10 charactersand mixedcase?> I'll look into set schema thanks for the tip, I should have mentioned though
our production data is on a totally separate box so no worries there. All of
our library lists are controlled and managed and QTEMP is always at the top
of the user portion of the LIBL.





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
dieter.bender@xxxxxxxxxxxx
Sent: 30 October 2010 15:42
To: Midrange Systems Technical Discussion
Subject: Re: SQL database object names longer than 10 charactersand mixed
case?

congratulation, I have seen problems more than once, creating Files in
QTEMP, and writing to the original production table...
One problem with naming *SQL is the implicit connect, normally you would
have to connect to the database, before sending SQL statements to it and for

test purpose you would connect to a diffrent database, but set schema would
work too, to switch from production to test.

D*B


--------------------------------------------------
From: "Neill Harper" <neill.harper@xxxxxxxx>
Sent: Saturday, October 30, 2010 1:58 PM
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Subject: RE: SQL database object names longer than 10 charactersand
mixedcase?> We don't let users randomly change their library list and we
control what
files go where in the library list.

It's never been a problem. May be I am wrong because I don't come from a
green field site. We have lots RPG and SQL working with each other all
over
the place, loads of OVRDBF's and CRTDUPOBJ's to QTEMP, all that lovely
goodness that keep u head scratching.

When we use *SYS naming it plays nice, when we use *SQL it doesn't.

Also we have over 30 test environments on our dev box all sharing the same
code base but with different data (controlled by library list) again *SQL
does not allow this (or more accurately I have never been able to get it
to
work).

This makes me question, have we taken the wrong approach to test env's,
how
are you guys doing it?

Thanks

neill

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
dieter.bender@xxxxxxxxxxxx
Sent: 30 October 2010 07:27
To: Midrange Systems Technical Discussion
Subject: Re: SQL database object names longer than 10 charactersand mixed
case?

.. must be a joke, you have a database supporting referential integrity
constraints and then you are saying "I don't mind where the item comes
from
belonging to the order". LIBL is great for programs, but not for locating
tables or views.

D*B

--------------------------------------------------
From: "Neill Harper" <neill.harper@xxxxxxxx>
Sent: Saturday, October 30, 2010 12:31 AM
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Subject: RE: SQL database object names longer than 10 charactersand
mixedcase?> They are all good reasons, but in a strange way they are all
the
opposite
of
why I like *SYS. I originally came from a PC .net background and when I
was
first introduced to the iSeries Library list I couldn't believe how much
flexibility it offers.

There is nothing like it out there on the other RDBMS's and is up there
in
my eyes with the classpath!!

This is something you lose when you use *SQL.

Anyway each to their own :-)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: 29 October 2010 20:02
To: Midrange Systems Technical Discussion
Subject: RE: SQL database object names longer than 10 characters and
mixed
case?


First, just to remind myself I'm using a full-featured, modern database
on
i.

Second, to keep consistent with other database engines I might have to
use.

Third, to keep my skills portable.

I could probably come up with more, but those top the list at the moment.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Neill Harper
Sent: Friday, October 29, 2010 1:33 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL database object names longer than 10 characters and
mixed
case?

Just out of interest, what are your reasons for using SQL naming
convention?




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: 29 October 2010 18:26
To: Midrange Systems Technical Discussion
Subject: RE: SQL database object names longer than 10 characters and
mixed
case?


I use long names religiously.

create table rjsflow.somelongname ... ;

select * from rjsflow.somelongname;

Notice I also use SQL naming convention. Just as religiously. I can do
this
on a 5250 from STRSQL or more often from OpsNav or java JDBC.

DB2/400 stores the long names somewhere; I don't know where and I don't
need
to know. DB2/400 will make up a short name (or I can use the LABEL
statement) for the name it puts on the file in the library. For most of
the
stuff I do, I don't ever use the short name.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Murvin
Sent: Friday, October 29, 2010 11:27 AM
To: Midrange Systems Technical Discussion
Subject: SQL database object names longer than 10 characters and mixed
case?

I gather that is is possible to have SQL database object names on the
System
i that are longer than 10 characters and mixed case. This could be SQL
tables, views, triggers, etc. I just can't see where they would be used
or
stored. Perhaps in the IFS?

Has anyone actually used these long names, and if so, could you give me
an
example? (Not the actual SQL code, but just a sample name, where you
would
store in on the system, and what type of application would use it.)

Thanks.

--
Dave Murvin

www.drmetools.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.



--
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.

--
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.



--
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.

--
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.


--
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.

--
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.


--
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.

--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.