Well supported? ... i do try my best :D
I'm running a few farms on 1.17 and some standalones on 1.19 (i
think?!), but i'm in the process of switching all of them to 1.21 once
it's officially out and i manage to port some of our in-house extensions.
Oracle versions on all of them have just been
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
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
OK, let me try to clarify this issue a bit. I know Akshay understands
the concept as we have talked about this for about a week before he even
started this project but i guess he is not using the right terms for the
message to come across.
Basically what you're asking is Why use native MW
May i barge into this discussion a bit and please, feel free to shut
me down if i'm missing a point here.
I'm failing to see why all this debate. We already have transactions, we
have begin, commit and rollback in the abstraction (Database.php lines
2830+). And this works. All that needs
I was also thinking about introducing a similar functionality, not
exactly nested transaction but just a way to prevent $db-commit and
$db-rollback from doing enything.
Akshay(my GSoC) wanted to have his extension code transaction safe, but
there was just no way of doing it without tinkering
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
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
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'll have a look(haven't poked the phpunit code for a while now) to make
sure it's operational on Oracle backend.
@Chad: if the issue is in the DB itself (i inderstand that running it
can be somewhat of a pain) i could try to get you access to one of out
sandbox instances for the purposes of
Well for starters the read rights for addon namespaces would be a nice
first step.
On 21. 07. 2011 20:35, Andrew Garrett wrote:
On Thu, Jul 21, 2011 at 11:14 AM, Casey Brownli...@caseybrown.org wrote:
Just a note that I think our stance on per-page access restrictions
has always been: Do
Havent read the whole thread, but why not just do it the ol' school way.
Have texvc create two images one with alpha and the other without, and
then serve formula images depending on the user-agent. I know this is a
nasty patch, IE6 and similar users remain at current state, while the
others
bitNot, bitAnd, bitOr functions implemented and replaced hardcoded
operators in SQL code with function calls. Did some testing, but i never
trust my own testing so, please have click or two.
l8r, Jure
___
Wikitech-l mailing list
I never said my solution was unbreakable, didn't even say it's good ...
far from it ... I just said that the solution can be implemented there,
but after your SamMax example i'm starting to doubt my way would work.
So on that note i'm for what's behind door number 3 ... the second version
$sql
be in the key part of the array
makeList solution would work ...
Freako F. Freakolowsky wrote:
I never said my solution was unbreakable, didn't even say it's good ...
far from it ... I just said that the solution can be implemented there,
but after your SamMax example i'm starting to doubt my way
Why was this approach opposed?
I am working on Oracle abstraction at the moment and i was planning to
implement such a function.
DJ Bauch wrote:
I would much rather see a function added at the Database
class level to form compound queries from subqueries, since the
alternative is to introduce
16 matches
Mail list logo