Hi Victor, KEY is what is used to create the indexes.
Excerpt for the MySQL documentation: "KEY is normally a synonym for INDEX. The key attribute PRIMARY KEY can also be specified as just KEY when given in a column definition. This was implemented for compatibility with other database systems." Benoit. On Wed, Jul 14, 2010 at 7:12 AM, Victor Engmark <[email protected]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I couldn't find any in my current branch except the one I created for my > own table, and after `git checkout master` and `git pull` I get the > following: > > $ grep -i '\sindex.*(' ~/src/invenio/modules/miscutil/sql/tabcreate.sql > INDEX (reply_order_cached_data(40)) > INDEX (reply_order_cached_data(40)) > > Where can I find a revision with more indexes? > > PS: I don't mean primary key indexes, which AFAIK are created > automatically, but rather indexes for columns which are queried often > for equality (for example `id_user = %d`). > > Cheers, > > On 07/14/2010 11:40 AM, Benoit Thiell wrote: > > Hi Victor, > > > > indexes are created for lots of Invenio tables. Please refer > > to modules/miscutil/sql/tabcreate.sql. > > > > Benoit. > > > > On Wed, Jul 14, 2010 at 4:54 AM, Roman Chyla <[email protected]> wrote: > > > >> 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: > > 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/> > “Pulling together is the aim of despotism and tyranny. Free men pull in > all kinds of directions. […] It’s the only way to make progress.” > Havelock Vetinari in “The Truth”, by Terry Pratchett > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJMPZuyAAoJEMj+WTFE4nA6UFYH/iYBrLTsKM7qZVcl9nhgB+vE > 4lIkF5RfvtpdjK1TKGbJ10BofRUOlPaGUB5FeAPcbPSaVJn8qZw1sEVDi03AHQwv > xmgb3+OQOJTERuGoCQpt0/m0s2E2xJkbKNyuoIVMR42x1JmkO1ZLcbkK2vnmMMgO > 1Qb8qYqtXwjhOgRVHtpMG5SDgoZd4/Waj35YLWHjiKwKc4d/XQnnkz3QsCXt//o/ > jK5Ryv70l69vDuiPp4/BB29Rw57CIz77la9N9Bnz5Fx/i7dkFqdrWstTgl10TQBg > T6E0yoCiWBijcmrfaOgvpfkf1EWCGO9zpN11cHgz605JBEDqxoGCYsytbidM5ik= > =OyDy > -----END PGP SIGNATURE-----
