[05:31:26] <CptViraj>	 If I make a table schema change (like adding a new column) in my non-_p ToolsDB database, do I need to manually update the _p version as well?
[09:07:07] <dhinus>	 CptViraj: in ToolsDB, _p tables are independent from the non-_p tables, there's no automatic update.
[09:11:33] <CptViraj>	 dhinus: I see, but when I push changes to the data (inserting or deleting rows) in the non-_p table, it automatically reflects in the _p table. So, unlike schema changes, the data is replicated automatically, right?
[09:13:42] <dhinus>	 if you tell me the name of the table I can double check. maybe the _p table is defined as a view referencing the non _p table.
[09:14:05] <dhinus>	 even in that case, you would need to update the view definition if the referenced table changes
[09:16:17] <CptViraj>	 s56898__gipbe_audit
[09:19:27] <dhinus>	 looking
[09:22:19] <dhinus>	 the _p table is indeed a view referencing the non-_p table, so it reflects the data from the non _p table
[09:22:46] <dhinus>	 but in MariaDB, views definitions are not updated automatically if you change the referenced table
[09:23:40] <dhinus>	 so if you add a new column in the non-_p table, it won't be visible in the view until you update or recreate the view
[09:25:37] <dhinus>	 you should be able to see the view definition with "SHOW CREATE TABLE s56898__gipbe_audit_p.gipbe_audit;"
[09:27:16] <CptViraj>	 Aha, tyvm :)
[09:30:38] <dhinus>	 yw!
[10:56:13] <TMWYK>	 !log tools.enderbot-dev will initiate its database in two days, which might log errors. I apologise for it in advance (but I hope it all goes well)
[10:56:15] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.enderbot-dev/SAL