Hi, Correct me someone if I am wrong, but not using foreign keys is not that uncommon in many CMSs (though special indices are often created, not only those for PRIMARY and UNIQUE keys as in Invenio). I don't believe constraints are maintained by Python (how could they be, unless one uses some object relational mapper like sqlalchemy?) and that is another reason for dealing with constraints manually, ie. writing the query by hand, also for other CMSs. It is forcing some different approach to executing queries, especially, if they should be portable amongst many RDMS.
roman On Wed, Jul 14, 2010 at 10:27 AM, Victor Engmark <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > Is anyone using native MySQL foreign keys / unique constraints / indexes > at all in Invenio? For example, the only place I could find creation of > an index is in modules/bibrank/lib/bibrank_citation_indexer.py, and > that's just for a temporary table. Are constraints maintained in Python? > Has anyone benchmarked those compared to MySQL constraints? And how do > you survive performance-wise without indexes? > > - -- > Victor Engmark <http://l0b0.wordpress.com/> > “Work Safely! Accidents cause meetings!” > Unknown source > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJMPXTgAAoJEMj+WTFE4nA6kLQIAI4encfEjQB49JRyzBrTu8Gm > VG1z9meP5OwpjdpjNiWvR745eaSP4eSYbBwz8FPvLRJLbfzFdGILyt8IkGJ2zY9V > WFNCZsZ06OOj7qLWW8XTVSWcqx72+k1M3+uKjk02VKsceLPR3Lm4VnUNxDP9t+ta > siSlvdYVqyMPtjj20Q9mTeYlgljtrYKhFpMSFFohuAQ1DMmyP075BKHJdEUCVEEh > 0tJqr83YaWPj6GrGwEYh1GjocKn4A7luWhyAL20xd36hkX+Jzj38qrfqDIkkzr88 > 4zfeix8ux4PJPP62JUqyDK2MoI7O75qyFrilPXjjY8Da+KT2s4osx4gMpJj110c= > =XQ+R > -----END PGP SIGNATURE----- >
