Freako F. Freakolowsky wrote:
I think it would be about time to start practicing what we preach (like,
that MW is a great knowlagebase tool) and move all these comments to
mw.org database manual pages.
It's handy to have all those comments in the code, but to clutter the
schema abstraction
On Sun, Apr 22, 2012 at 6:36 PM, Greg Sabino Mullane g...@endpoint.com wrote:
Platonides wrote:
Note we will also need a way to generate a SQL from that (eg.
for manually creating a new database with SQLAdmin).
Personally, I prefer viewing the code (SQL) which is really
used, but I won't
On 25. 04. 2012 20:25, Greg Sabino Mullane wrote:
Freako F. Freakolowsky wrote:
I think it would be about time to start practicing what we preach (like,
that MW is a great knowlagebase tool) and move all these comments to
mw.org database manual pages.
It's handy to have all those comments in
Le 18/04/12 18:09, Greg Sabino Mullane wrote:
I'm jumping back into the abstract schema project
Are we reinventing the wheel once again or is that a project to select
and integrate an existing tool?
--
Antoine hashar Musso
___
Wikitech-l mailing
I think it would be about time to start practicing what we preach (like,
that MW is a great knowlagebase tool) and move all these comments to
mw.org database manual pages.
It's handy to have all those comments in the code, but to clutter the
schema abstraction code over those comments is just
Antoine hashar Musso wrote:
Are we reinventing the wheel once again or is that a project
to select and integrate an existing tool?
I'm open to using something existing: did you have something
specific in mind? I didn't see anything out there that would
be less trouble to customize than
Doctrine does versioning of databases in PHP:
http://www.doctrine-project.org/
On Mon, Apr 23, 2012 at 7:47 AM, Greg Sabino Mullane g...@endpoint.comwrote:
Antoine hashar Musso wrote:
Are we reinventing the wheel once again or is that a project
to select and integrate an existing tool?
Platonides wrote:
Note we will also need a way to generate a SQL from that (eg.
for manually creating a new database with SQLAdmin).
Personally, I prefer viewing the code (SQL) which is really
used, but I won't stop you from making the perfect abstraction.
Well, the very first task of the
Chad wrote:
I think we should probably work on mediawiki.org (subpage of
RfC?). This is something that needs to be thought out properly,
and I think on-wiki would be more productive than on-list.
Okay. I will create an RFC page. Keep in mind that my time is limited
and I've only just started
On Fri, Apr 20, 2012 at 5:27 PM, Greg Sabino Mullane g...@endpoint.com wrote:
Krinkle wrote:
I'd say put it in Gerrit from the start (in a branch) so that everyone
can check it out and send suggestions (either as a commit or through the
feedback channels on the mailing list, wiki or Gerrit
On 20/04/12 23:27, Greg Sabino Mullane wrote:
Right. I've been thinking about this a lot, and the big picture plan
is to remove all the tables.sql files and create a single text file,
mediawiki.schema, which will have a generic schema, very similar to
the existing main tables.sql, but with
count me in :D
On 18. 04. 2012 18:09, Greg Sabino Mullane wrote:
I'm jumping back into the abstract schema project, and was
wondering what the workflow is for something like this. Should
I simply create a new branch and have everybody (assuming other
people have an interest) collaborate on that
I'm jumping back into the abstract schema project, and was
wondering what the workflow is for something like this. Should
I simply create a new branch and have everybody (assuming other
people have an interest) collaborate on that branch until we
are ready to start involving gerrit? Obviously,
On Wed, Apr 18, 2012 at 12:09 PM, Greg Sabino Mullane g...@endpoint.com wrote:
I'm jumping back into the abstract schema project, and was
wondering what the workflow is for something like this. Should
I simply create a new branch and have everybody (assuming other
people have an interest)
On 18/04/12 18:09, Greg Sabino Mullane wrote:
I'm jumping back into the abstract schema project, and was
wondering what the workflow is for something like this. Should
I simply create a new branch and have everybody (assuming other
people have an interest) collaborate on that branch until
On Apr 18, 2012, at 6:09 PM, Greg Sabino Mullane wrote:
I'm jumping back into the abstract schema project, and was
wondering what the workflow is for something like this. Should
I simply create a new branch and have everybody (assuming other
people have an interest) collaborate on that
16 matches
Mail list logo
