Subject | Re: [Firebird-Architect] Autonomous Transaction Routines |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2007-11-09T15:37:15Z |
Alex Peshkov escreveu:
That means we can, for example, work with images but can't render GUI. :-)
Adriano
> On Friday 09 November 2007 18:25, Doug Chamberlin wrote:We must predict common usage scenarios to introduce features...
>
>> At 09:31 AM 11/9/2007, Adriano dos Santos Fernandes wrote:
>>
>>> 1) A common usage pattern of autonomous transaction will be to insert one
>>> row in a table.
>>>
>> I would like to caution everyone about making such assumptions. Once a
>> feature is added there will be every possible variation tried, often in
>> ways we have not yet envisioned. Therefore, you CANNOT predict the "common
>> usage pattern".
>>
>Of course. And can work for more complex cases like an IF or WHILE. :-)
> Certainly. Adriano wanted to say that in case of single operator per
> autonomous transaction suggested by me and implemented by him syntax is
> specially effective.
>
>FWIW, Oracle JVM running in database uses headless AWT.
>> If you want to add a feature in support of a specific usage pattern please
>> try to do it in a way that limits or prevents variations and
>> re-interpretations of the original intent. The perversity of user
>> contortions has no bounds! Look at what people are always trying to do
>> using UDF's!!
>>
>
> :))) It's a great pity use of windows GUI was not disabled in UDFs! (But how
> could it be done?)
That means we can, for example, work with images but can't render GUI. :-)
Adriano