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



By Jove, I think you've got it!  Especially the last paragraph.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





qsrvbas@xxxxxxxxxxxx (Tom Liotta)
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/13/2003 10:34 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     midrange-l@xxxxxxxxxxxx
        cc: 
        Fax to: 
        Subject:        RE: SQL date comparison - a better way?


midrange-l-request@xxxxxxxxxxxx wrote:

>   4. RE: SQL date comparison - a better way? (rob)
>
>You're questionable about the new fields needing the maintenance program 
>recompiled.  If I add a field that converts a 6 digit date into a true 
>date field, the maintenance on that could easily be handled with a 
>trigger.  However, in a perfect world, the maintenance program would use 
a 
>true date field and the trigger would convert that into the 6 digit date 
>field for compatibility with the other programs.  Thus getting the right 
>date and not having to use a cut off date.

Rob, I don't see near enough of other techniques for such things, but it 
seems to me that, for most shops, a trigger program that modifies/converts 
values between fields is an example of a maintenance program that ought to 
be recompiled when fields are added to the underlying table. For "most 
shops", that is. Yours may be better.

While buffer offsets to locate the record images are supplied, the actual 
record structure may have changed. I'd want to be certain the new 
structure was brought in. This is not nearly as important in the 
methodology that you advocated where new fields are always added at the 
end, but I'd tend to be cautious anyway.

I also see that you may mean that rather than "re-compiling" an existing 
maintenance program, you can instead extend the file maintenance portion 
of the application by creating, compiling and adding a new trigger. Seems 
reasonable. Part of my appreciation of the whole relational database 
concept is the ability to extend an existing database without disrupting 
current function.

Tom Liotta

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertechgroup.com


__________________________________________________________________
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial 
today!
http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397

Get AOL Instant Messenger 5.1 free of charge.  Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
_______________________________________________
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 ...

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.