On 28. 02. 2013 04:29, Greg Sabino Mullane wrote:
I can't think of a clean way to abstract that anyway, as just needing
an index hint for MySQL does mean the same is needed on Oracle, and
vice-versa.
Please don't use index hints on Oracle ... since 9i you get far better
performances using CBO
Daniel Friesen let us know:
For reference this is the RFC that was discussed in my thread on the
subject.
https://www.mediawiki.org/wiki/Requests_for_comment/Abstract_table_definitions
Should probably dig up some gmane/archive links for both this and that
discussion and add them to
Matthew Flaschen wrote:
No, I was just talking about defining the indices (obviously, the query
planner is out of luck if you don't define them properly). E.g. in the
PostgeSQL tables.sql file:
CREATE INDEX archive_name_title_timestamp ON archive
(ar_namespace,ar_title,ar_timestamp);
For reference this is the RFC that was discussed in my thread on the
subject.
https://www.mediawiki.org/wiki/Requests_for_comment/Abstract_table_definitions
Should probably dig up some gmane/archive links for both this and that
discussion and add them to the RFC page.
--
~Daniel Friesen
Luke Welling asked:
Specifically, do we use MySQL specific syntax that is more efficient (but
breaks elsewhere) or do we attempt to write lowest common denominator SQL
that will run more places, but not run as efficiently on our primary target?
Neither: we use the already-existing methods, and
On 02/27/2013 10:29 PM, Greg Sabino Mullane wrote:
Not sure what you mean - index hints? Yeah, that could be a little tricky,
but luckily the Postgres part, at any rate, doesn't have to worry about
those (as our planner is smart enough to pick the best index itself ;).
I can't think of a
On 26/02/13 04:18, Matthew Flaschen wrote:
Sure, for starters. :) Bear in mind, if we want to keep support for all
these dbs, every change to the database schema has to (at some point)
result in a change to separate SQL files for each DB (MySQL and SQLite
use the same ones). For instance, there
26 Февраль 2013 г. 14:27:06 пользователь Nikola Smolenski (smole...@eunet.rs)
написал:
On 26/02/13 04:18, Matthew Flaschen wrote:
Sure, for starters. :) Bear in mind, if we want to keep support for all
these dbs, every change to the database schema has to (at some point)
result in a
Do we have an official position on cross database compatibility?
Some of the MediaWiki SQL is in separate files and can be easily directed
at a specific database engine. A lot of it though is scattered as
fragments though other code and is going to be run on any engine we connect
to.
On 02/26/2013 02:14 PM, Luke Welling WMF wrote:
Do we have an official position on cross database compatibility?
It would be nice if we did. In my own production environments, I always
use postgres. To date, mw has been good enough with its support that
I've never had significant
On 02/26/2013 02:14 PM, Luke Welling WMF wrote:
Specifically, do we use MySQL specific syntax that is more efficient (but
breaks elsewhere) or do we attempt to write lowest common denominator SQL
that will run more places, but not run as efficiently on our primary target?
There's a DB layer
How can we improve the support for databases like PostgreSQL, Oracle,
DB2 and MS SQL?
Getting Jenkins involved in testing isn't the (only) answer, though it
would certainly help.
If developers who were interested in those databases could watch
includes/db, that would help, as well.
If nothing
I would be happy to install some mediawiki on oracle db, but I have no
oracle db on any of my personal servers :/
The main problem of oracle is that it's not very much free - thus it's
not packaged by most of linux vendors and it might be hard to install
for many sysadmins. (In order to install
On Mon, Feb 25, 2013 at 9:27 AM, Mark A. Hershberger m...@everybody.org wrote:
How can we improve the support for databases like PostgreSQL, Oracle,
DB2 and MS SQL?
The main issues arise from not keeping these other DBs in mind when
writing the queries (and also not using the db layer).
On Mon, Feb 25, 2013 at 7:27 AM, Mark A. Hershberger m...@everybody.org wrote:
Getting Jenkins involved in testing isn't the (only) answer, though it
would certainly help.
If developers who were interested in those databases could watch
includes/db, that would help, as well.
The latter is
On 02/25/2013 10:40 AM, Chad wrote:
Covering all the non-mysql/sqlite we support:
- DB2 has been unmaintained for ages, and personally I'm in favor
of dropping that one altogether.
- MSSQL would be nice to improve.
- Oracle support's not bad (maybe not perfect), freakolowsy would
know more.
I'm still alive and willing to continue to work on MSSQL.
On Mon, Feb 25, 2013 at 9:40 AM, Chad innocentkil...@gmail.com wrote:
On Mon, Feb 25, 2013 at 7:27 AM, Mark A. Hershberger m...@everybody.org
wrote:
Getting Jenkins involved in testing isn't the (only) answer, though it
would
On 02/25/2013 10:52 AM, Danny Joe Bauch wrote:
I'm still alive and willing to continue to work on MSSQL.
Have you tried to run MediaWiki's latest from git against MSSQL?
--
http://hexmode.com/
There is no path to peace. Peace is the path.
-- Mahatma Gandhi, Non-Violence in Peace and War
No. The last version I got running was 1.19, and have not worked on any
since. I could do as you suggest, though.
On Mon, Feb 25, 2013 at 9:54 AM, Mark A. Hershberger m...@everybody.orgwrote:
On 02/25/2013 10:52 AM, Danny Joe Bauch wrote:
I'm still alive and willing to continue to work on
It would be best to have automated environment for this, either on
labs or somewhere else. Problem is that it's not possible to install
MSSQL and such on wikimedia labs given the restrictions
On Mon, Feb 25, 2013 at 5:36 PM, Danny Joe Bauch dj.ba...@gmail.com wrote:
No. The last version I got
On 02/25/2013 11:43 AM, Petr Bena wrote:
It would be best to have automated environment for this, either on
labs or somewhere else. Problem is that it's not possible to install
MSSQL and such on wikimedia labs given the restrictions
Which is why I suggested that we work with someone at MS to
Microsoft was very kind to provide me with an Azure account which I used to
do the testing of 1.18 and 1.19. I've not been in touch with them lately,
nor have I checked whether that account is still open. I would gladly jump
back on that. I'm afraid I got a bit distracted when my job disappeared
There are some bugs that also prevents accurate unit testing on multiple
backends (these are the ones I hit personally):
* *Bug 37702* https://bugzilla.wikimedia.org/show_bug.cgi?id=37702 - Cloned
tables for unittests do not have references and constraints
* *Bug 44790*
On 02/25/2013 07:40 AM, Chad wrote:
On Mon, Feb 25, 2013 at 7:27 AM, Mark A. Hershberger m...@everybody.org
wrote:
Getting Jenkins involved in testing isn't the (only) answer, though it
would certainly help.
If developers who were interested in those databases could watch
includes/db, that
On Mon, Feb 25, 2013 at 7:48 AM, Mark A. Hershberger m...@everybody.org wrote:
Other than that, I can only add my +1 to dropping DB2 support. I don't
know of it being used anywhere.
https://gerrit.wikimedia.org/r/#/c/50764/
-Chad
___
Wikitech-l
On Mon, Feb 25, 2013 at 9:53 AM, Sumana Harihareswara
suma...@wikimedia.org wrote:
* Make a meta-schema so that we no longer use tables.sql as a canonical
source. Chad and Max started in
http://svn.wikimedia.org/viewvc/mediawiki/branches/abstract-schema/ .
See
I'm still active on Oracle front, but as you might have noticed i have
been [WARNING ... understatement ahead] a bit busy in the last 1,5 year
so i just can't manage to pay as much attention to what's going on as i
would like to ...
I used to get paid by my company to do this, but due to some
Mark A. Hershberger wrote:
How can we improve the support for databases like PostgreSQL, Oracle,
DB2 and MS SQL?
Getting Jenkins involved in testing isn't the (only) answer, though it
would certainly help.
If developers who were interested in those databases could watch
includes/db, that
On Mon, Feb 25, 2013 at 1:29 PM, Greg Sabino Mullane g...@endpoint.com wrote:
Mark A. Hershberger wrote:
How can we improve the support for databases like PostgreSQL, Oracle,
DB2 and MS SQL?
Getting Jenkins involved in testing isn't the (only) answer, though it
would certainly help.
If
Where is the abstract-schema branch now? The only thing I remember about
that was a brief mailing list discussion (I think started by Daniel
Friesnen) about making such a format. What exactly were the hold-ups with
updates?
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major
On Mon, Feb 25, 2013 at 2:00 PM, Tyler Romeo tylerro...@gmail.com wrote:
Where is the abstract-schema branch now? The only thing I remember about
that was a brief mailing list discussion (I think started by Daniel
Friesnen) about making such a format. What exactly were the hold-ups with
However - it's not a freeware and that automatically makes it very
unpopular for open source OS vendors and very unlikely a choice of
standard webadmin and that makes it hard to test. Even if I was able
to obtain some license to install oracle on any of my servers, I
wouldn't do it as it
Oh. Sorry must have missed that. I'll take a look and see if there's
anything interesting.
On Feb 25, 2013 5:05 PM, Chad innocentkil...@gmail.com wrote:
On Mon, Feb 25, 2013 at 2:00 PM, Tyler Romeo tylerro...@gmail.com wrote:
Where is the abstract-schema branch now? The only thing I remember
On 02/25/2013 12:53 PM, Sumana Harihareswara wrote:
The question: what do we need to test more often to keep RDBMSes happy?
https://www.mediawiki.org/wiki/Database_testing
https://www.mediawiki.org/wiki/New_installer/Test_plan Permissions,
searching, schema setup, schema changes, quoting
34 matches
Mail list logo
