Hi all,
Is it possible to store data into user tables through queries on
Wikireplica DBs? Or is it only possible by mysqldump'ing from the replica
DB and loading into the user table in a separate step?
I am thinking of aggregate data.
Thanks!
___
Wikimedi
No, the wikireplicas are read-only.
That said, ToolsDB (Toolforge user DB) is not equipped to handle
becoming an aggregate datamart for the wiki replicas at any thing close
to large (wiki) scale--just small chunks that are ideally regularly
cleaned up. Are we talking about a database on a Cloud VP
I was thinking of running a query, temporarily store its output on ToolsDB.
Join it with some other query and then throw it away. All in small scale
and for short-term.
On Fri, May 8, 2020 at 5:01 PM Brooke Storm wrote:
> No, the wikireplicas are read-only.
>
> That said, ToolsDB (Toolforge user
Hmm, does create temporary table work? If not, can it?
Martin
On Fri, May 8, 2020, 11:04 PM Huji Lee wrote:
> I was thinking of running a query, temporarily store its output on
> ToolsDB. Join it with some other query and then throw it away. All in small
> scale and for short-term.
>
> On Fri,
Temporary tables are awesome! But they are session-dependent. I am thinking
of a scenario in which different scripts (different sessions) would
generate data sets in parallel, and then they are combined.
Obviously, I can do all of this using flat file data dumps (what I do right
now). But I was tr
On Fri, May 8, 2020 at 3:01 PM Brooke Storm wrote:
>
> No, the wikireplicas are read-only.
There is slightly more context for this restriction in the blog post
that announced the "new" Wiki Replicas databases in 2017 [0].
The prior generation of Wiki Replica databases did allow arbitrary
table c
One clarification,
While everything Bryan says is right, I have to say that the main factor in
not allowing writes on wikireplicas wasn't pain for administration (which
was real) as much as avoiding continuous blockage of data due to other
users creating long-running write queries (pain for users)
