Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: database tool, consistency check and report, sanitzation  (Read 6073 times)

0 Members and 1 Guest are viewing this topic.

icefox

  • Guest
database tool, consistency check and report, sanitzation
« on: November 17, 2006, 12:00:41 AM »

Hello guys,

We merged services DB's and ran with em a while good.
But now, real bad issues come up.

Features i request are:

1. ORE graph of Database
2. RDBMS backend, fully usable ( drop off these db files plz! )
( think of using table lockings and transactions, guys!!! )
- Try stay within SQL standard and provide db modules for major database backends like, postgres, MySQL, ... , oracle, sybase, adabas, db2, whatever..
- People would more likely develop codes if they can easily and understandable look over your db structure.

3. database sanity tool -> reports and fixes DB
( MAJOR ISSUE )
anopes service db doesnt show up sanity to me.
A sane database structure would not allow collisions or broken dbs...

If your in need of someone to provide standard database access code snippets, i can write you database access modules for postgres and maybe other ones.
The other thing which has to come from your side is use of standard SQL language, which offers all you need to do this data access and lock stuff.

Im lookin forward for comments.
Logged

SpaceDoG

  • Anope User
  • Offline Offline
  • Posts: 183
    • http://www.hypermutt.net
(No subject)
« Reply #1 on: November 17, 2006, 03:27:44 PM »

icefox,

Anope MySQL support will not be in until version 2.0. At present the devs have no idea when this will be. I know it's been a slow progression over the past year (that I've known about it) and it will probably continue to be so. Also at present Anope will load the database from SQL if you tell Anope to use MySQL. Therefor, to merge DB's all you have to do is load each db into a seperate MySQL database and then merge the databases and drop colliding nicks.
Logged

icefox

  • Guest
(No subject)
« Reply #2 on: November 17, 2006, 03:57:23 PM »

I can confirm it didnt work here.
Anope started up with a clean database and didnt use the MySQL.
Commenting out .db files also didnt work.

Options that have been set were UseRDB and SecureMySQL.

version is 1.7.17
Logged

SpaceDoG

  • Anope User
  • Offline Offline
  • Posts: 183
    • http://www.hypermutt.net
(No subject)
« Reply #3 on: November 17, 2006, 04:48:08 PM »

Did you type /msg operserv set sql on as well as compiling anope with myqsl support?
Logged

Pieter Bootsma

  • Team
  • *
  • Offline Offline
  • Posts: 189
    • http://geniusdex.net/
(No subject)
« Reply #4 on: November 17, 2006, 07:33:57 PM »

We are aware that our current MySQL implementation is very poor compared to how it should be. We've planned that there won't be a completely replacement of this until after version 1.8, but it's one of the top priority points afterwards.
Logged
Pages: [1]   Go Up