How come edits take longer to load than new posts?

[Jaguar]

Just curious. It generally takes me three times as long as a new post to edit. The loading time from the edit post screen to that little intermediary screen is so long that it is actually more efficient to press back and refresh after I submit.

[Kuciwalker]

that it is actually more efficient to press back and refresh after I submit.

That's what I always do

[Sarxis]

I've always wondered about this too. Is it just the page refresh that is taking so long?

-edit-

Yup.

[Asher]

Edits require more queries that take longer.

For new posts it just adds an entry at the end of the table, for editing posts it needs to search for the old entry in the table, then change it.

[Ecthy]

I asked before, stated my theory and it was correct.

[Alex]

i never edit my posts - they're always the Absolute Truth (TM).

[Urban Ranger]

Originally posted by Asher
Edits require more queries that take longer.

For new posts it just adds an entry at the end of the table, for editing posts it needs to search for the old entry in the table, then change it.

No it doesn't. Because it has already serached and found the entry it needed. It's just an UPDATE query.

[MarkG]

it's not a single update query in the posts table. there are more queries having to do with the search index which must kept updated

[Asher]

Originally posted by Urban Ranger
No it doesn't. Because it has already serached and found the entry it needed. It's just an UPDATE query.

When will you learn enough to not argue with me when it comes to computers?

[Solver]

BTW Markos, it seems that delete queries on post database don't remove the posts from search index...

[mrmitchell]

Let's imagine that you have a stack of 10 books. "A" is at the bottom, then B, C, D, E, F, G, H, I, "J". Now, you add book "K" to the top of the stack.

You remember an inaccuracy in book F. You must get out F and correct the mistake. To do so, you have to carefully slide out F from the stack (or take the top half of the stack off), then change it, then carefully put it back in where it was. That takes more work than just adding a book to the top, doesn't it?

[Urban Ranger]

Originally posted by MarkG
it's not a single update query in the posts table. there are more queries having to do with the search index which must kept updated

But don't you need to create those entries in the first place?

[Urban Ranger]

Originally posted by mrmitchell
You remember an inaccuracy in book F. You must get out F and correct the mistake. To do so, you have to carefully slide out F from the stack (or take the top half of the stack off), then change it, then carefully put it back in where it was. That takes more work than just adding a book to the top, doesn't it?

Yes, but only for a stack of books

[Gramphos]

Originally posted by Urban Ranger


But don't you need to create those entries in the first place?

They are created, but now they have to be deleted, and new have to be created. All words longer than four(?) chatracters have to be linked to the postid, and if it is a new word it has to be added to the word table.

[Urban Ranger]

I see, thanks