Quoting Rickard Öberg Rickard Öberg <[email protected]>: > On 2010-08-02 13.42, Stanislav Muhametsin wrote: > > Well it is faster to have BIGINT as table primary key, instead of > > VARCHAR(infty). It is used, for example, when adding new entities. It is > > also used in associations and many-associations - instead of referencing > > entity by identity-string, it is referenced by entity primary key > > (BIGINT). Additionally, each qualified name in its own table references > > entity through the primary key. > > I thought you only had a clob-type binary with the JSON for the > EntityState. Are you saying that the EntityStore splits up associations > into other tables? > > > Primary key is not exactly indexed - it just is there so that it could > > be referenced from other tables instead of using potentially very long > > string, which may be replicated all over the database, as pretty much > > every table references entity in some way. > > What tables? I thought there was only one?
Stanislav talk here about the SQLIndexing which can be synchronized with the EntityStore if both are used together. Plus, in the ES itself we reference the entity_pk column during updates and deletions. Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
