What are the minimum required tables that require rows to be added to create user, so is then visible active in discourse Ive just inserted one row into user_emails insert into user_emails (user_id, email, "primary", created_at, updated_at) values (2,'user@email.com',true, now(), now()); Unsuprisingly has not appeared in the gui, but what are the minimum steps, do I need to add to some more tables, or is there some restart I need to do. Now I expect someone will say this is not the right ways to do things, and I understand that, but for me it might be as I’ll explain below (some of my assumptions may be incorrect but this is my understanding) All the import scripts that import from another database based forum expect to be able to connect to the other forum from the discourse instance. But being able to access the other forum (jforum) from live discourse instance is going to be difficult if not impossible, similarly trying to install a discourse dev environment where by old forum resides (very old server) is also not possible. I dont understand Ruby on Rails so I cant modify the existing scripts, but I do understand SQL I could use the API (I only have 5000 users) but I want to be able to plugin/method that keep the md5 password hash rather than requiring all users to reset their passwords so I don’t think I can do this using the API There is a jforum import script so I can use that to look at the SQL required to get data out of jforum no problem to then put into csv files to load into database. The bulk importers possibly provide the way to add SQL into discourse but struggling to see the SQL. Seems getting the users in is the key thing, then adding categories, topics and posts should not be so hard.

Sorry, but I am going to close this off as “please don’t do that” Too risky, and there are many side effects you are likely to forget.

[image] paultaylor: ow I expect someone will say this is not the right ways to do things, Right! [image] paultaylor: and I understand that, If you did, you’d not be asking. :wink: The likelihood that you’ll end up with a corrupt database is pretty high. And then no one will be able to help you. Dump your database and restore on your local Discourse server (or anywhere that it can connect to–I’ve done larger imports with a remote database over my home internet connection) and then run the existing script. [image] paultaylor: dont understand Ruby on Rails so I cant modify the existing scripts, but I do understand SQL It’ll be much easier to use Ruby that you don’t understand than to understand it well enough to figure out how to write the SQL. I learned Ruby a long time after I wrote my first importer.

[image] pfaffman: If you did, you’d not be asking. That is a bit condesensing ! If the bulk import script is running sql (as I think it is)then documenting the SQL required to create a user is really no more dangerous then trying to use a bulk import script. And since I currently have a vanilla discourse install it wouldn’t terribly matter it if got messed up.I expect I have many more years in development than yourself. What I don’t have great experience is all the admin tasks, and my first attempt to install a local Discourse server just opened a can of worms, and if I cant connect to my JForum mysql server from my discourse server then I’m going to have to install mysql as well and transfer the database. The existing jforum script isn’t checked into the main source tree, and Im on a very old version of jforum so not expecting it to work.

[image] paultaylor: That is a bit condescending! I meant no offense. I guess you missed the :wink:? [image] paultaylor: I expect I have many more years in development than yourself. I bet you’re right! Sometimes free advice from someone that’s worked with Discourse full time for over three years, has done scores of imports, and written several importers from scratch is worth what you pay for it.

[image] paultaylor: connect to my JForum mysql server from my discourse server How about setting up an SSH tunnel? [image] pfaffman: a corrupt database Inconsistent, maybe. Corrupt, no. [image] paultaylor: want to be able to plugin/method that keep the md5 password hash rather than requiring all users to reset their passwords so I don’t think I can do this using the API But you can create the users using the API and then insert the md5 hashes in a custom field using SQL. You will have best of both worlds.

[image] michaeld: But you can create the users using the API and then insert the md5 hashes in a custom field using SQL. You will have best of both worlds. Yes, I had the thought but as I dont quite understand how the md5 hashing works wasn’t clear if that was possibility, okay I will give that a go.

All you need to do is insert a custom field: user_id: obvious name: “import_pass” value: the md5 digest And install the migratepassword plugin.

Thanks, have a few questions I hope you can help me with. Installation Run bundle exec rake plugin:install repo=http://github.com/[Communiteq](https://www.communiteq.com) (formerly DiscourseHosting)/discourse-migratepassword in your discourse directory Restart Discourse I have installed it, but how do I restart Discourse ? How do I insert the custom field, can you give the SQL, or it can it be done with the api with the "user_fields[1]": "string" part. I am now programmatically able to create user via api but Im currently ignoring this field. If you have the plugin installed, is the value of password passed as part of api creat user call irrelevant.

no, it will prevail over the md5 digest in the custom field. The answers to the other two questions can easily be found on this forum. If you want to save time we can do the import and/or hosting for you as a paid service.

I did search for both answers, was unable to find. In the first case it is confusing that some installs are done via editing the yaml file and then relaunching the docker , and some seem such as this are installed whilst in the docker container, its not cxlear what restart means in this case. I cant really find any pure sql in this forum Surprised there seems such a push to sale paid services for using this opensrc software , never like this when i ask questions on stackoverflow.

How to create a new user in pure sql

Product Support Migration

michaeld (Michael - Communiteq) December 19, 2019, 10:39pm 5

How about setting up an SSH tunnel?

Inconsistent, maybe. Corrupt, no.

But you can create the users using the API and then insert the md5 hashes in a custom field using SQL. You will have best of both worlds.

Topic		Replies	Views
Migrated password hashes support Plugin	34	12995	June 2, 2026
Reset password with custom ruby file Development	9	1026	September 27, 2023
Migrate a bbPress WordPress plugin forum to Discourse Migrating to Discourse how-to	33	13621	January 10, 2024
Best tools, materials & practices to onboard a hoarde of new users? Community Building	22	4137	January 30, 2018
Use an import script that requires MySQL Sysadmins how-to	51	13851	December 12, 2023

How to create a new user in pure sql

Related topics