Import data from IPBoard

NodeBB Development

Suggested Topics


  • 1 Votes
    3 Posts
    416 Views

    @baris yeah it's true, but you can use transaction on a multicluster with only one node, also if with a lot of limitations.
    About your command example is a good idea also if it would work only with redis and postgre, with mongodb can be used like a normal batch.

    I took a look to postgreSQL module, seems it support transactions, mongodb emulate the same thing with non ACID batch. I prefer to avoid SQL databases but the way data is organized seem more suitable to a relational DB

  • 0 Votes
    9 Posts
    2k Views

    Yes, it is this plugin : https://github.com/nodebb/nodebb-plugin-global-chat

    Some night, tongues are loosened, and it seems to be interesting to keep a "short history" (such as 24h) of the global chat.

  • 0 Votes
    1 Posts
    2k Views

    I am writing a plugin.

    Can anybody pl. write the code pattern for this requirement of mine...

    When a logged in user enters some data, the backend should do the following in response:

    The user sends the data to the NodeBB backend in the following format:
    { key1: data-value1, key2: data-value2, ... }

    Get the user id of the user and check if the key1, key2, etc. already exists in the Mongo DB (the user's collection/document)

    If yes, overwrite the data

    If not, store the data

    Tell the client that the action has been taken

    Actually, it is quite simple if you're writing an app from the scratch. What I am looking for is the pattern/way the NodeBB is currently handling this scenario and I want to code using the same pattern.

    Thanks

  • 0 Votes
    6 Posts
    2k Views

    @riddle911 nice job. I may good at programming but I'm definitely not an expert in Excel. Nice work, and thanks for sharing.

  • 0 Votes
    8 Posts
    4k Views

    @baris thanks!

    I don't like to brag 😛 but I kinda figured this out 16h ago

    I was checking uid==0 and skipping that out from deletion, but kept getting deleted. My admin uid kept incrementing for every node app --setup, so I looked at the schema again.

    but thanks your helper methods were extremely helpful.