SELECT * FROM cl_configs0.00092697143554688Всего 0.00092697143554688 секMysqliDb->get() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/tools.php" line #1406
SELECT * FROM cl_ui_langs WHERE status = '1' 0.00022983551025391Всего 0.0011568069458008 секMysqliDb->get() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #1659
SELECT
u.id,
u.username,
u.avatar,
u.followers,
u.posts,
u.following,
u.country_id,
u.website,
u.about,
u.last_active,
u.is_online,
u.fname,
u.lname,
u.email,
u.verified,
u.follow_privacy
FROM cl_users u
WHERE u.active = '1' AND u.id != 0
ORDER BY u.followers DESC, u.posts DESC
LIMIT 50.00599479675292969Всего 0.0071516036987305 секMysqliDb->rawQuery() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #1005
SELECT
h.id,
h.tag,
h.posts,
COUNT(DISTINCT p.user_id) AS unique_users,
COUNT(*) AS posts_count,
MAX(ph.time) AS last_activity
FROM cl_hashtags h
JOIN cl_publications_hashtags ph
ON ph.hashtag_id = h.id
JOIN cl_publications p
ON p.id = ph.publication_id
WHERE CHAR_LENGTH(h.tag) >= 2
AND ph.time >= NOW() - INTERVAL 7 DAY
GROUP BY h.id
HAVING unique_users >= 1
ORDER BY unique_users DESC, last_activity DESC
LIMIT 15;
0.09423804283142090Всего 0.10138964653015 секMysqliDb->rawQuery() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/post.php" line #385
SELECT * FROM cl_publications WHERE status IN ( 'active', 'inactive', 'deleted' ) AND id = '619' LIMIT 10.00034213066101074Всего 0.10173177719116 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/post.php" line #699
SELECT * FROM cl_users WHERE id = '233' LIMIT 10.00049090385437012Всего 0.10222268104553 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #1859
SELECT * FROM cl_users WHERE id = '233' LIMIT 10.00045895576477051Всего 0.1026816368103 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #230
SELECT * FROM cl_publications WHERE thread_id = '619' AND status IN ( 'active', 'inactive', 'deleted' ) ORDER BY id DESC LIMIT 300.00034117698669434Всего 0.103022813797 секMysqliDb->get() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/apps/thread/app_ctrl.php" line #95
UPDATE cl_publications SET `views_count` = views_count+1 WHERE id = '619' 0.00274896621704102Всего 0.10577178001404 секMysqliDb->update() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/post.php" line #23
Posting Changesets
Perforce has a concept of changesets, which are server-stored descriptions of a change along with an ID number and associated files. For Perforce, Review Board stores changeset numbers of a posted change and can use these to associate particular changes with review requests.
To post a review request for a specific change, or to update an existing review request for that change, type:
$ post-review CHANGENUM
Where CHANGENUM is the changeset number in Perforce.
The diff will be generated and uploaded to Review Board, and the review request information will be update
Perforce has a concept of changesets, which are server-stored descriptions of a change along with an ID number and associated files. For Perforce, Review Board stores changeset numbers of a posted change and can use these to associate particular changes with review requests.
To post a review request for a specific change, or to update an existing review request for that change, type:
$ post-review CHANGENUM
Where CHANGENUM is the changeset number in Perforce.
The diff will be generated and uploaded to Review Board, and the review request information will be update
