Yes. Comments stay in wp_comments and wp_commentmeta. wpDiscuz adds AJAX submission, real-time updates, voting, ratings, and follows, but the comment text and threading still live in core tables. Anything reading core comments — Akismet, exports, REST endpoints — keeps working unchanged.

wpDiscuz adds tables for subscriptions, comment votes, post ratings, and user follows. Exact names depend on the version installed, but each is keyed by the parent comment or post ID. SleekView's agent UI auto-discovers them and offers them as joinable sources without you typing a table name.

Yes. Edit the status cell on many rows and save once. SleekView writes through wp_set_comment_status(), the same function the default Comments screen uses, so spam filters, notification emails, and any custom transition_comment_status hooks fire correctly for every changed row.

Yes. SleekView's writes use standard WordPress hooks rather than direct SQL updates. Akismet observes the comment lifecycle through wp_set_comment_status, so an approval done in SleekView is indistinguishable from an approval done in the default Comments screen as far as Akismet's learning is concerned.

Yes. Vote tallies live in the wpDiscuz vote table keyed by comment_id. SleekView joins that table onto wp_comments and exposes positive count, negative count, and the difference as separate columns — sort by net score or filter by minimum downvotes.

Yes. wpDiscuz add-ons typically extend wp_commentmeta or add their own keyed tables. SleekView reads wp_comments as the base and lets you join any auxiliary table on a shared key, so add-on data shows as additional columns in the same view.

Yes. SleekView views can be private to a user or shared with specific roles. A common setup: a moderation queue shared with the moderator role, a featured-comments view shared with editors, and a subscriber audit shared only with the data-protection officer. Each role lands on the right table on first click.

Re-open the agent UI, point SleekView at the renamed table, and your existing views update. Joins are configured by name in SleekView's storage, so a wpDiscuz schema change is a one-time reconfiguration rather than a data-loss event. Nothing in wp_comments itself is touched.