Magma with style

[Igor Stasenko]

On 10 December 2010 02:59, Chris Muller <ma.chris.m at gmail.com> wrote:
> Yes, I'm not surprised that takes 3 minutes.  The first problem is
> that you are using an invalid operator in your where.  You must use
> "equals:", not "=".  But the bigger problem is the design.  There is
> overhead to using #where:, especially when using a disjuction or
> sorting or eliminating duplicates.  End-user search and querying is
> the primary use-case for the #where: operations, not using Magma as a
> RDBMS to "look-up" single objects by a key value.  The right
> collection for that job is MagmaPreallocatedDictionary, which can be
> large (millions) and still provide very fast #at: access to one object
> at a time.  I do not recommend MagmaDictionary or MagmaSet where
> performance is at all concerned.  For that reason these collections
> really deserve to be deprecated and deleted from Magma.
>

Whis makes me think that the problem lying in API.
I think that Magma could provide an API, which will let users to do
thing in most efficient way,
without much hassle.
Especially for people with big RDBMS background (most of us ;).

> The right way to use Magma is to do things as object-oriented as
> possible, and only rely on MagmaCollections for applying
> value-indexing to the objects.  Is documentNumber extrinsic to the
> system, or is it a relational pointer to a Document object?
>
> Regards,
>  Chris
>
>
>


-- 
Best regards,
Igor Stasenko AKA sig.