= would be safer but a lot slower to go through 100k + of records.
Query 'jake.jacobson' would require post-processing ...
-
mjacobson
- Posts: 204
- Joined: Fri Feb 08, 2002 3:35 pm
-
mark
- Site Admin
- Posts: 5519
- Joined: Tue Apr 25, 2000 6:56 pm
Query 'jake.jacobson' would require post-processing ...
Not with an index (regular, not metamorph).
-
Kai
- Site Admin
- Posts: 1272
- Joined: Tue Apr 25, 2000 1:27 pm
Query 'jake.jacobson' would require post-processing ...
Not with a regular index on userid; should be somewhat faster than with Metamorph. Presumably userid values don't get very large (more than a KB or so) correct?
create index useridIndex on janesMasterLogs(userid);
UPDATE janesMasterLogs ... where userid = 'jake.jacobson';
Then you also avoid any Metamorph syntax issues, like a leading +/-/= sign for set logic, etc., or sub-string match issues, etc. Exact char-for-char match with =.
create index useridIndex on janesMasterLogs(userid);
UPDATE janesMasterLogs ... where userid = 'jake.jacobson';
Then you also avoid any Metamorph syntax issues, like a leading +/-/= sign for set logic, etc., or sub-string match issues, etc. Exact char-for-char match with =.
-
mjacobson
- Posts: 204
- Joined: Fri Feb 08, 2002 3:35 pm
Query 'jake.jacobson' would require post-processing ...
Thanks, that is much faster with the correct index built.