-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Shaun Murray wrote:
> In MySQL (and MS SQL IIRC) you can create full text indexes on char, =20
> varchar and text fields for faster and more advanced searching =20
> (relevance calcs, boolean operators, stopwords etc). See http://=20
> dev.mysql.com/doc/refman/5.0/en/fulltext-search.html
Note the disclaimer: it can only be used with MyISAM tables.
> Under Postgres, a quick google threw up this quite nasty module - =20
> http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/
Right, because Postgres has a btree index limit of around 2kb (I think).
Tsearch alleviates that problem but its usage, I agree, is a bit nasty
as it requires a new data type.
> To improve the searching in phpWebSIte I was thinking of going to =20
> full text indexes but it would appear Postgres will throw a spanner =20
> in the works.
>=20
> Anyone got any ideas or will I be doing..
>=20
> if Mysql { fancy way } else { old way }
I would say "if table type =3D=3D mysql myisam {fancy way} else {old way}=
"
would be preferred ;-)
I think it's great in theory and, if you can check table type, I say go
ahead and use it at the module level. As for sticking it in core, I'd
have reservations.
My humble =A30.02.
kw
- --
Kevin Wilcox
http://ess.appstate.edu
http://www.appstate.edu
Office: 828.262.6740
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFFLPSKsKMTOtQ3fKERAvnKAKCgcb7wDMCKCM1uKua9wgSPYy9g3ACfYUZD
K31HjSGpNTB/rMX6/jQDrvw=3D
=3DhyBI
-----END PGP SIGNATURE-----
|
