Developer
  • Projects
  • Docs
  • Blog
  • Forum
  • Builds
  • BLENDER.ORG

    • Download

      Get the latest Blender, older versions, or experimental builds.

    • What's New

      Stay up-to-date with the new features in the latest Blender releases.

    LEARNING & RESOURCES

    • Blender Studio

      Access production assets and knowledge from the open movies.

    • Manual

      Documentation on the usage and features in Blender.

    DEVELOPMENT

    • Developers Blog

      Latest development updates, by Blender developers.

    • Documentation

      Guidelines, release notes and development docs.

    • Benchmark

      A platform to collect and share results of the Blender Benchmark.

    • Blender Conference

      The yearly event that brings the community together.

    DONATE

    • Development Fund

      Support core development with a monthly contribution.

    • One-time Donations

      Perform a single donation with more payment options available.

Logo
Explore
Products
Blender User Manual Developer Documentation
Blender Benchmark
Blender Studio Tools Flamenco Watchtower
Modules
Animation & Rigging Asset System Core Grease Pencil Modeling Nodes & Physics Pipeline & I/O Platforms & Builds Python API & Text Editor Sculpt, Paint & Texture Triaging User Interface VFX & Video
Rendering
Render & Cycles Viewport & EEVEE
Report a Bug Paste Code Help
Sign In
archive/phabricator
1
0
Fork 0
You've already forked phabricator
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
Files
bcd0caecd17437b933bb5121b09ebcb7deb908c1
phabricator/resources/sql/patches/20131030.repostatusmessage.sql

10 lines
395 B
MySQL
Raw Normal View History

Add "RepositoryStatusMessage" and detailed information about initilization Summary: `RepositoryStatusMessage` is basically a key/value table associated with a repository that I'm using to let the daemons store the most recent event of a given type, so we can easily show it on the status dashboard. I think this will be a lot easier for users to figure out than digging through logfiles. I'm also going to write the "this needs a pull" status here eventually, for reducing the time lapse between pushes and discovery. - Add storage for these messages. - Have the pull engine populate the INIT phase. I'll do the FETCH phase next. - Update the status readout to show all the various states. Test Plan: See screenshots. Reviewers: btrahan Reviewed By: btrahan CC: aran Differential Revision: https://secure.phabricator.com/D7461
2013-10-30 16:04:19 -07:00
CREATE TABLE {$NAMESPACE}_repository.repository_statusmessage (
id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,
repositoryID INT UNSIGNED NOT NULL,
statusType VARCHAR(32) NOT NULL COLLATE utf8_bin,
statusCode VARCHAR(32) NOT NULL COLLATE utf8_bin,
parameters LONGTEXT NOT NULL,
epoch INT UNSIGNED NOT NULL,
UNIQUE KEY (repositoryID, statusType)
) ENGINE=InnoDB, CHARSET utf8;
Reference in New Issue Copy Permalink
Powered by Gitea Page: 63ms Template: 2ms
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API