SELECT * FROM cl_configs0.00052309036254883Всего 0.00052309036254883 сек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.00017499923706055Всего 0.00069808959960938 сек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.00457096099853516Всего 0.0052690505981445 сек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.07847809791564941Всего 0.083747148513794 секMysqliDb->rawQuery() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/post.php" line #385
SELECT id FROM cl_users WHERE username = 'vewovo9476' LIMIT 10.00021886825561523Всего 0.083966016769409 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #671
SELECT * FROM cl_users WHERE id = '233' LIMIT 10.00026297569274902Всего 0.084228992462158 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #230
SELECT * FROM cl_users WHERE id = '233' LIMIT 10.00024795532226562Всего 0.084476947784424 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #357
SELECT * FROM cl_publications WHERE user_id = '233' AND profile_pinned = 'Y' LIMIT 10.00019216537475586Всего 0.08466911315918 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/apps/profile/app_ctrl.php" line #128
SELECT posts.`id` as offset_id, posts.`publication_id`, posts.`type`, posts.`user_id`, posts.`time` FROM `cl_posts` posts
INNER JOIN `cl_publications` pubs ON posts.`publication_id` = pubs.`id`
WHERE posts.`user_id` = 233
AND pubs.`profile_pinned` = "N"
ORDER BY posts.`id` DESC
LIMIT 15;
0.00015187263488770Всего 0.084820985794067 секMysqliDb->rawQuery() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/apps/profile/app_ctrl.php" line #37
SELECT * FROM cl_publications WHERE status IN ( 'active', 'inactive', 'deleted' ) AND id = '619' LIMIT 10.00014114379882812Всего 0.084962129592896 сек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.00022888183593750Всего 0.085191011428833 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #230
SELECT * FROM cl_publications WHERE status IN ( 'active', 'inactive', 'deleted' ) AND id = '618' LIMIT 10.00016117095947266Всего 0.085352182388306 сек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.00022697448730469Всего 0.08557915687561 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #230
SELECT * FROM cl_publications WHERE status IN ( 'active', 'inactive', 'deleted' ) AND id = '617' LIMIT 10.00015187263488770Всего 0.085731029510498 сек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.00023007392883301Всего 0.085961103439331 секMysqliDb->getOne() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/user.php" line #230
UPDATE cl_publications SET `views_count` = views_count+1 WHERE id = '619' 0.00310206413269043Всего 0.089063167572021 секMysqliDb->update() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/post.php" line #23
UPDATE cl_publications SET `views_count` = views_count+1 WHERE id = '618' 0.00088286399841309Всего 0.089946031570435 секMysqliDb->update() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/post.php" line #23
UPDATE cl_publications SET `views_count` = views_count+1 WHERE id = '617' 0.00063109397888184Всего 0.090577125549316 секMysqliDb->update() >> file "/var/www/twitty/data/www/ai.twitty.ru/twitty_web/core/components/post.php" line #23
4 г. назад
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
4 г. назад
Depending on the repository type, post-review will either require a changeset number, or it will rely on the changes in the current source tree. The end result is that post-review will build a diff and post it to a Review Board server. The diff and any additional review request information will be saved on the server as a draft, which can then be published.
After posting a new review request or updating an existing one, post-review will display the URL of the review request. If the -o parameter is passed, a browser will be opened to that URL.
The following subsections will explain how po
After posting a new review request or updating an existing one, post-review will display the URL of the review request. If the -o parameter is passed, a browser will be opened to that URL.
The following subsections will explain how po
4 г. назад
post-review is a command line tool for Windows, Linux and MacOS X that simplifies both creating and updating review requests. It can look at your source directory, generate a diff, and upload it to a new or existing review request on an associated Review Board server. This saves a lot of time over the web UI, and for some types of code repositories (such as Perforce), it’s actually required in order to produce a compatible diff.
post-review is part of the RBTools package, and can be installed and upgraded by runnin
post-review is part of the RBTools package, and can be installed and upgraded by runnin
