Scoreboard

[Cubical]

why don't you just keep track of high scores on a notepad. if internet goes down u have hard copy

[Inari]

Originally Posted by Cubical

why don't you just keep track of high scores on a notepad. if internet goes down u have hard copy

Possible, but that isn't very dynamic, and doesn't make much sense.
It makes sense to store player-data in a central place where its easily accessible via a language made for accessing such entries

[fowlplay4]

Originally Posted by Cubical

why don't you just keep track of high scores on a notepad. if internet goes down u have hard copy

i also backup all my data to offsite stone tablets.

[Tim_Rocks]

Originally Posted by Cubical

why don't you just keep track of high scores on a notepad. if internet goes down u have hard copy

Cubical brings up an excellent point here.

[Inari]

Pros of SQL (some only apply if using a primarily SQL-based system, so probably not to all graal servers ):

• Easy access to all data
• Made to store and request data (and has proven itself)
• Doesn't break from staff editing the attributes
• Better relational data management

among others

(Of course storing all data in NPC-flags is also a way, but then you end up having to write more potentially slower and buggier script code)

[Tim_Rocks]

Yea, but there's no need to create an SQL table for over a thousand players when all you really need is 25 of them.

[Inari]

Originally Posted by Tim_Rocks

Yea, but there's no need to create an SQL table for over a thousand players when all you really need is 25 of them.

Well, no direct /need/, except if you use SQL to begin with Which maybe graal servers should consider doing... I guess its more of a point of "hey, if you put your structure more around SQL you can make such things much much easier"~

[Cubical]

Originally Posted by Inari

Well, no direct /need/, except if you use SQL to begin with Which maybe graal servers should consider doing... I guess its more of a point of "hey, if you put your structure more around SQL you can make such things much much easier"~

Well, no direct /need/, except if you use SQL to begin with Which maybe graal servers should consider doing... I guess its more of a point of "hey, if you put your structure more around SQL you can make such things much much easier"~

[Inari]

Originally Posted by Cubical

Well, no direct /need/, except if you use SQL to begin with Which maybe graal servers should consider doing... I guess its more of a point of "hey, if you put your structure more around SQL you can make such things much much easier"~

Well, no direct /need/, except if you use SQL to begin with Which maybe graal servers should consider doing... I guess its more of a point of "hey, if you put your structure more around SQL you can make such things much much easier"~
(am i missing something?)

Anyway, my original point still is valid I guess: If you use SQL you have a much cleaner code and the < 1 MB you use to store data doesn't bother anyone ever.

[Cubical]

Originally Posted by Inari

Well, no direct /need/, except if you use SQL to begin with Which maybe graal servers should consider doing... I guess its more of a point of "hey, if you put your structure more around SQL you can make such things much much easier"~
(am i missing something?)

Anyway, my original point still is valid I guess: If you use SQL you have a much cleaner code and the < 1 MB you use to store data doesn't bother anyone ever.

Well, no direct /need/, except if you use SQL to begin with Which maybe graal servers should consider doing... I guess its more of a point of "hey, if you put your structure more around SQL you can make such things much much easier"~
(am i missing something?)

Anyway, my original point still is valid I guess: If you use SQL you have a much cleaner code and the < 1 MB you use to store data doesn't bother anyone ever.

[Tim_Rocks]

I use SQL for most systems on Era. Works nicely.

[Carlito]

SQL is great i use it mostly but at the same time it can easily be abused and bloat your db. If Snk only wanted the top 20 players why would he store and update over 3000 accounts. I feel for this reason his method is best, it is only maintaining the top 25 oppose of all 3000+ players. DB npcs are great for temp storage especially on situations like this.

[prozacboy666]

Use SQL. Here is how I would do it.
When a new score comes in do a select on the database for the minimum score to get into the top20.

PHP Code:

SELECT MIN(score) FROM myTable; 


If new score > min, insert new score into the database and delete the min score.
The only thing is you would have to do two queries to delete the min score from the database something like

PHP Code:

minId = SELECT id FROM myTable WHERE score = (SELECT min(score) FROM myTable)
DELETE FROM top20 WHERE id = minId 


Then all you have to do is selects on that table if you are looking for the top20

PHP Code:

SELECT * FROM top20 ORDER BY score DESC 


You probably could get the ID and delete it from the database all in one query but this should be fast enough.

[Elk]

Originally Posted by fowlplay4

i also backup all my data to offsite stone tablets.

cuneiform <3

[xAndrewx]

Originally Posted by prozacboy666

Use SQL. Here is how I would do it.
When a new score comes in do a select on the database for the minimum score to get into the top20.

PHP Code:

SELECT MIN(score) FROM myTable; 


If new score > min, insert new score into the database and delete the min score.
The only thing is you would have to do two queries to delete the min score from the database something like

PHP Code:

minId = SELECT id FROM myTable WHERE score = (SELECT min(score) FROM myTable)
DELETE FROM top20 WHERE id = minId 


Then all you have to do is selects on that table if you are looking for the top20

PHP Code:

SELECT * FROM top20 ORDER BY score DESC 


You probably could get the ID and delete it from the database all in one query but this should be fast enough.

You'd need three queries.
1,) Find the minimum score
2,) Add the score
3,) Delete old score


I guess it's what you want to store.