36 results

• User Documentation

  The Drizzle Wiki is no longer stored here. Please see www.drizzle.org/wiki/User_Documentation

  https://drizzle.fandom.com/wiki/User_Documentation

• Coding Standards

  Indent level is done with 2 spaces (a vimrc collection that does our style can be found here: http://hg.tangent.org/vimrc (Someone needs to answer how to get Emacs to do this)) M

  https://drizzle.fandom.com/wiki/Coding_Standards

• Developer list

  An incomplete list of people working on the project, as a guide for other developers. https://launchpad.net/~brianaker

  https://drizzle.fandom.com/wiki/Developer_list

• Drizzle Contributors

  The Drizzle Wiki is no longer stored here. Please see www.drizzle.org/wiki/Drizzle_Contributors

  https://drizzle.fandom.com/wiki/Drizzle_Contributors

• Build Slave Issues

  The Drizzle Wiki is no longer stored here. Please see www.drizzle.org/wiki/Build_Slave_Issues

  https://drizzle.fandom.com/wiki/Build_Slave_Issues

• Testing Infrastructure

  ? Details[] Restarts of the server during a crash, Comparing results of a slave and a master, Easy creation of new tests Some queries generate thousands of values Not all test results are ordered. Expected

  https://drizzle.fandom.com/wiki/Testing_Infrastructure

• Proposed Testing Protocol

  The Drizzle Wiki is no longer stored here. Please see www.drizzle.org/wiki/Proposed_Testing_Protocol

  https://drizzle.fandom.com/wiki/Proposed_Testing_Protocol

• FAQ

  Brian Aker explains: A micro-kernel that we then extend to add what we need. All additions come through interfaces that can be compiled/loaded in as needed. The target for the project is web

  https://drizzle.fandom.com/wiki/FAQ

• Table Proto Definition

  In the process of eliminating the need for FRM we have to define a message system and at the same time upgrade the serialized table definition. The current proposal is to use Google's Proto

  https://drizzle.fandom.com/wiki/Table_Proto_Definition

• New Protocol

  STATUS: This is currently a proposed draft as of October 25, 2008 Drizzle Protocol ---------------- The Drizzle protocol works over TCP, UDP, and Unix Domain Sockets (UDS, also known as IPC sockets), although there are limitations

  https://drizzle.fandom.com/wiki/New_Protocol

• Simple Replication

  The goal of this development is to develop a very simple and lightweight replication for use in a cloud. In order to quickly deploy a solution, this replication implementation will be statement-based and will

  https://drizzle.fandom.com/wiki/Simple_Replication

• Open Discussions

  Testing Protocol (TP) proposal Licensing[] server licensing - GPL2, because it's inherited., plugin/client licensing - anything (GPL2, BSD says Brian), contributor policies/agreement -- none, Documentation licensing (GFTL or Creative Commons or dual), packaging/repository options

  https://drizzle.fandom.com/wiki/Open_Discussions

• BuildBot

  The success of Drizzle will be due to the contributions of the community. You don't have to be a coder to contribute, there are many other areas including testing, documentation and contributing to the

  https://drizzle.fandom.com/wiki/BuildBot

• Contributing Code

  You need Bazaar for revision control. bzr launchpad-login [yourloginid] You should prepare a directory to keep bzr work in mkdir$repo# where$repos is some directory (ex:~/repos) cd$repo bzr init-repo drizzle

  https://drizzle.fandom.com/wiki/Contributing_Code

• Logos

  Proposed Logo 1 Proposed Logo 2 Proposed Logo 3 Proposed Logo 4 Proposed Logo 5 Proposed Logo 6 Proposed Logo 7 Proposed Logo 8 Proposed Logo 9 Proposed Logo 10 Proposed Logo 11 Favicon.ico

  https://drizzle.fandom.com/wiki/Logos

• Debugging drizzle with GDB

  To use GDB, this is what I typically do... Build the server with debugging symbols (--enable-debug) into/tmp using the attached script, then:

  https://drizzle.fandom.com/wiki/Debugging_drizzle_with_GDB

• Team:BugKillers

  This is the home page for the Drizzle Bug Killers community contributor team. We're responsible for finding, fixing, and otherwise eradicating bugs from Drizzle. Listed below are blueprint tasks and bug reports that are

  https://drizzle.fandom.com/wiki/Team:BugKillers

• Tasks that need help

  The Drizzle Wiki is no longer stored here. Please see www.drizzle.org/wiki/Tasks_that_need_help

  https://drizzle.fandom.com/wiki/Tasks_that_need_help

• Test Automation Framework

  The Drizzle Wiki is no longer stored here. Please see www.drizzle.org/wiki/Test_Automation_Framework

  https://drizzle.fandom.com/wiki/Test_Automation_Framework

• TODO

  Everything has been moved to https://blueprints.launchpad.net/drizzle

  https://drizzle.fandom.com/wiki/TODO

• Starting drizzled

  The Drizzle Wiki is no longer stored here. Please see www.drizzle.org/wiki/Starting_drizzled

  https://drizzle.fandom.com/wiki/Starting_drizzled

• Testing

  The Drizzle Wiki is no longer stored here. Please see www.drizzle.org/wiki/Testing

  https://drizzle.fandom.com/wiki/Testing

• Drizzle Community Standards

  Be Good. The drizzle community is committed to open and transparent contribution and doing good by the open source community. Here is a list of our ideals and goals: We are welcoming, We welcome everyone

  https://drizzle.fandom.com/wiki/Drizzle_Community_Standards

• Drizzle History

  Drizzle began as a fork of the MySQL 6.0 codebase around April/May 2008. The project was announced at OSCon 2008 by Brian Aker, one of the founding Drizzle developers.

  https://drizzle.fandom.com/wiki/Drizzle_History

• About Drizzle

  Drizzle: A High-Performance Microkernel DBMS for Scale-Out Applications Drizzle is a community-driven project based on the popular MySQL DBMS that is focused on MySQL's original goals of ease-of-use, reliability

  https://drizzle.fandom.com/wiki/About_Drizzle