Relational Database Question .....

[Alma J Wetzker]

My recommendation would be to go with SQL as the standard syntax.  Build a 
utility to change the old source to the new and ship it with the working 
system.  There may well be compelling reasons to make *NO* changes to the 
AppGen syntax, if so, fine.  If not, some simple, judicious changes like 
updating standard database commands to SQL seem like a Real Good Idea (tm)

     -- Alma

Ben Duncan wrote:
> On my SLAG project (The OSS AppGen replacement based in S-Lang I am 
> writing),
> in order to emulate on of the aspects of Appgen, which is:
> 
> When in a screen and you are on the "record key" prompt, which is 
> usually prompt
> number 1, after entering the data, the runtime does a read to the 
> primary file.
> If it gets a hit, it automagically puts you in "Change" mode and 
> populates the
> data portion of that screen, if it does not get a hit, the runtime then 
> asks if
> you wish to "add" the record as new (using the just entered key value).
> 
> I just figured to do a "READ" using the key to do the same for SLAG.
> 
> Suggestions, criticism, alternate solutions?
> 
> FWIW: IANASE (I am not a SQL expert)
> 
> Kurt Wall wrote:
> 
>> On Tue, Dec 28, 2004 at 10:11:45AM -0600, Ben Duncan took 25 lines to 
>> write:
>> ; Does anyone know of any of that any of the database's out there can let
>> ; you access by giving a key and a read other than issuing a SQL command?
>>
>> Not really. I suppose you could cobble something together by creating 
>> a stored procedure, but the benefit would be pretty minimal.
>>
>> ; example (pseudo coded):
>> ; ; Select unique customer_number from customer ....
>> ; being the SQL code ...
>> ; ; READ customer using customer_number.
>> ; being the direct read .....
>>
>> If I ask why, would the answer matter?
>>
>> Kurt
> 
>