×
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.
Well, I agree that a document should be created. But not necessarily for
the users. The users need a decent view.
Let's say you have a table like this:
CREATE TABLE QTEMP/PAULIE (BIGCHARCOL CHAR (50 ) NOT NULL)
Now create a view like this:
create view qtemp/paulieV as (select
cast(substring(bigcharcol,1,3) as char (3)) as slsname,
cast(substring(bigcharcol,4,2) as decimal (2,0)) as mynbr
from qtemp/paulie)
Now if a spew a row into this table like
insert into qtemp/paulie values('ROB42')
I can do this
select * from qtemp/paulieV
and see
....+....1....
SLSNAME MYNBR
ROB 42
Why should the users have to do all that darn substringing on each and
every query? Have them query the view instead.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
