egghelp.org community

[innu]

[nml375]

Using xml might make it easier to alter the user database by hand. But you'd still have the issue of the userfile only being read once, and written every hour or so (making manually editing the userfile pretty pointless in most cases). In the rare occasion you'd have to repair your database manually, I'd probably think current format would be easier to fix by hand than xml. I'm sure there are a few good reasons to edit the database using various xml-tools, tho I'd considder those extremely rare (during my years since 1.0p and numerous botnets, I can count the number of times I've had to edit a userfile by hand on the fingers of my right hand...)

And since the data in the userfile always should be considdered old while your eggie is running, there really would'nt be much point in using any external tools to extract data while the eggie is running...

And as for mysql, I'm not too keen on having to install a mysqld and setting up databases and accounts with proper privileges, just in order to run an eggie.

Oh, and should I someday find a huge need to be able to modify my userlist from a fancy webpage with all the bells and whistles.. I'd just write a tiny script using sockets to allow my php-script to interface with my eggie under controlled conditions...
_________________
NML_375, idling at #eggdrop@IrcNET

[demond]

it would definitely make editing the userfile by hand easier, at least for novices (have you tried XML Notepad?)

but I actually meant another, more important advantage - now that people are used to mySQL db's storing and manipulating all kinds of webpage data, import/export & process eggdrop userfile in XML format would be possible with one-liner tools without any need of special SQL interface in eggdrop

and yes, it is an antiquated software - or to put it mildly, it isn't exactly what you call the bleeding edge of software development or at least a modern day software (my understanding is that there are some developments in integrating modern era technologies - 1.9 branch? - but given the pace of eggheads, we won't be seeing those released in stable builds anytime soon - if ever)
_________________
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use [code] tag when posting logs, code

[whittinghamj]

I this is a really old post but Its exactly what I am looking for - does anyone know of a script / module to make this happen?

Cheers

[nml375]

Currently, the user database is very much integrated in the core application, making it impossible to switch the non-volatile datastorage without extensive patching of the core.
That said, what can currently be done with scripts or modules, is to export a copy of the userfile into xml-data, mysqldump-data, or whatever flavor you desire. Performing this would be quite simple. This however, will not allow you to modify the user database from "outside" your eggdrop (that is, you'd still have to rely on eggdrops user database API in order to alter the database in any way).

The outlines for a script to export the database would be something like this, I suppose: