[Include] [BETA] BUD - Blazing User DB
#61

Is this still in beta stage or what?
Reply
#62

Quote:
Originally Posted by XStormiest
Посмотреть сообщение
How can i make the password to be case sensitive?
They are, when you save a password into the db it will save as you typed, I think.
And if you want them case insensitive just use tolower.

Quote:
Originally Posted by RedFusion
Посмотреть сообщение
Is this still in beta stage or what?
Yes.
Reply
#63

Quote:
Originally Posted by RedFusion
Посмотреть сообщение
Is this still in beta stage or what?
I've been using it for years with no problems


selecting a uid uses COLLATE NOCASE, so does registering a name however checkauth does not, I would suggest to make any name selections use COLLATE NOCASE by default
Reply
#64

Here's a tutorial that explains ALL of BUD functions.
Reply
#65

very nice
Reply
#66

Hmm, possible to change the limit?

BUD - Error: Too many entires passed to BUD::MultiSet; entires: 17, limit: 16.
Reply
#67

Quote:
Originally Posted by TitanZ
Посмотреть сообщение
Hmm, possible to change the limit?

BUD - Error: Too many entires passed to BUD::MultiSet; entires: 17, limit: 16.
pawn Код:
#define BUD_MULTISET_MAX_ENTRIES 32
#include <bud>
Reply
#68

Hi there!
BUD::Setting( opt.Asynchronous, true);
I heard, this will make it faster, however if something happens-database will be corrupted, can anyone explain about this? What if I want to keep it on, how do I prevent getting the database corrupted are there any possible ways?
Reply
#69

I cant download it, it says it can harm my pc.
I need another link
Reply
#70

Quote:
Originally Posted by Uberanwar
Посмотреть сообщение
Hi there!
BUD::Setting( opt.Asynchronous, true);
I heard, this will make it faster, however if something happens-database will be corrupted, can anyone explain about this? What if I want to keep it on, how do I prevent getting the database corrupted are there any possible ways?
Synchronous OFF mode basically writes the data without any sort of backup. If your program terminates or computer shuts down unexpectedly, you will have data loss and your db file will get corrupted if your have it OFF.

There are 3 types of syncs:
0 = OFF | 1 = NORMAL | 2 = FULL
(default is always FULL (2))

To avoid chances of corrupting database file, we use timers or close the database after some time to write changes to the .db file.


* If you trust your server, it will never crash, then use sync off without any worries and save data after good time intervals.
Reply
#71

Quote:
Originally Posted by Gammix
Посмотреть сообщение
Synchronous OFF mode basically writes the data without any sort of backup. If your program terminates or computer shuts down unexpectedly, you will have data loss and your db file will get corrupted if your have it OFF.

There are 3 types of syncs:
0 = OFF | 1 = NORMAL | 2 = FULL
(default is always FULL (2))

To avoid chances of corrupting database file, we use timers or close the database after some time to write changes to the .db file.


* If you trust your server, it will never crash, then use sync off without any worries and save data after good time intervals.
Closing the database won't guarantee safety in the event of a crash. In fact, I doubt it does more than just keeping it open.

Personally, I use the following, which gives both performance and safety:
pawn Код:
db_exec(db, "PRAGMA synchronous = NORMAL");
    db_exec(db, "PRAGMA journal_mode = WAL");
Luckily the horribly outdated SQLite implementation supports WAL.

@FrAnKiN1: Try now, I contacted ****** to remove that warning..
Reply
#72

anyone have new tutorial bud
Reply
#73

link down, anyone mirror pls?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)