Subject | Re: [Firebird-Architect] Re: EXECUTE STATEMENT |
---|---|
Author | Jim Starkey |
Post date | 2004-04-29T18:53:32Z |
Roman Rokytskyy wrote:
execution mechanisms (statement execution, expression evaluation, and
record streams) are high priority but outside the scope of Vulcan. The
basic idea is to reduce very complex problems into a system of very
simple solutions.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376
>>Practically speaking, I'd like to see both execution nodes and RSBsI want to take it mechanism by mechanism. The three primary engine
>>turned into proper type hierarchies before we do any major extensions.
>>Both are currently rather messy, to say the least. I think that
>>encapsulating those two systems before extending them will be about
>>half the work of extending them then encapsulating, and will result in
>>a much simpler, smaller system.
>>
>>
>
>If you accept solving current architectural issues module by module
>before changing that very module, and not first solving _all_
>architectural issues in the whole engine and only then allow
>extensions, then I support you with both hands.
>
>
execution mechanisms (statement execution, expression evaluation, and
record streams) are high priority but outside the scope of Vulcan. The
basic idea is to reduce very complex problems into a system of very
simple solutions.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376