how to separate first discussion and comment from posts table?

Hari

Hi, in posts table our flarum stores all first discussion and comments as comments.

how can I separate the first comment?

Hari

got it Number 1 means parent discussion .. its first comment!

using filter chose only number one .. you will get parent posts

clarkwinkelmann

From Flarum's point of view, the first post is just that, a comment. The first post always has number 1 so that's the way you could tell it apart.

I believe the only special handling in core is that we never add post number one to the URL, so /d/123-discussion/1 is just /d/123-discussion.

There is an issue about making the first post undeletable, to force users to correctly delete the discussion instead of the first post flarum/core2220

Extensions might do other things based on whether the post number is one, for example see-past-first-post hides everything except posts with the number one. The split post extension can cause the numbering to lack some numbers.

If you permanently deleted the first post but not the discussion, it's possible for a discussion to no longer have a post number one!

Hari

clarkwinkelmann flarum's database structure is really beautiful by spending 1hr i could easily understand how the core is storing* data.

we can import or export data easily while migrating to different platforms

do you usually use SQL querys to import flarum users/posts to WordPress? that is the easy way to avoid WordPress random numbering right?

clarkwinkelmann

Hari I'm not sure what you mean with the Wordpress queries. It's been a while I imported anything into Wordpress. I wasn't aware of any random IDs if that's what you mean? IDs are usually AUTO_INCREMENT MySQL columns and aren't managed by the software.

Hari

clarkwinkelmann

our flarum data has post id's and user id's

while I am importing data into WordPress using all import plugin .. WordPress changing post ids and user ids

how can we bypass this behaviour?

running a SQL query with 1000 lines (1000 users) will do our job?

/Edited

At MySQL level we should disable auto increment during the import : this will resolve the increment issue ?

clarkwinkelmann

Hari that sounds like something that should be offered as an option in the import plugin. Something like "preserve IDs".

If that import script is not copying existing IDs, then disabling AUTO_INCREMENT will just lead to errors since no ID will be provided during the insert.

When manually importing data via MySQL including IDs, there's no need to disable AUTO_INCREMENT. AUTO_INCREMENT will automatically pick up where it can once data with hard-coded ID has been inserted. If that's not the case, the current value of the AUTO_INCREMENT can be manually updated to start counting from another number.

Hari

INSERT INTOwp_users(ID,user_login,user_pass,user_nicename,user_email,user_url,user_registered,user_activation_key,user_status,display_name`) VALUES ([value-1],[value-2],[value-3],[value-4],[value-5],[value-6],[value-7],[value-8],[value-9],[value-10])

VALUES ([3],[ak],[ae8f1541bd926c61fa02879a21e9f0fa],[ak],[ak@gmail.com],[],[43922.5159722222],[],[],[ak])
VALUES ([4],[gb],[ae8f1541bd926c61fa02879a21e9f0fa],[gb],[gb@live.in],[],[43923.1909722222],[],[],[gb]) '

am I doing correctly?

edited : we should use ' instead of []