[LordMarqus]

Sure, it's not limited, I didn't say that. I mean this:

InnoDB stores data rows physically in primary key order while MyISAM typically stores them mostly in the order in which they are added. Storing the rows in primary key order corresponds to the MS SQL Server feature of “Clustered index” and the Oracle feature known as "index organized tables." When the primary key is selected to match the needs of common queries this can give a substantial performance benefit. For example, customer bank records might be grouped by customer in InnoDB but by transaction date with MyISAM, so InnoDB would likely require fewer disk seeks and less RAM to retrieve and cache a customer account history. On the other hand, inserting data in orders that differ substantially from primary key (PK) order presumably requires that InnoDB do a lot of reordering of data to get it into PK order. This places InnoDB at a slight disadvantage, in that it does not permit insertion order based table structuring.

We don't really need that and there are a lot of inserts. I think it decrease performance. Transactions are not used as well, all operations are made sequentially by the same user.

[altex]

I can not imagine css server that can show performance differences between sqlite, myisam and innodb I realy dont think it is a thing you should worry about. InnoDB is more powerfull engine, so i think it is better than myisam, that is why i choose it.

[LordMarqus]

Okay, let it be like that .

[LordMarqus]

I change to MyISAM. Even my hosting provider recommends that.

[altex]

Originally Posted by LordMarqus Hey. Do you know what such error could mean? L 12/12/2010 - 09:38:56: [knifetop.smx] Error saving player (The table 'knifetop' is full) Table has about 28000 entries. This error was repeating very long. Is that MySQL server problem?

it's because of mysql server settings.
try to change engine type

[kaskull]

How can I translate the menu?

[pubhero]

Hi.
I got many error messages / day from this plugin.
See:

L 01/17/2015 - 00:46:37: SourceMod error session started
L 01/17/2015 - 00:46:37: Info (map "de_dust2") (file "errors_20150117.log")
L 01/17/2015 - 00:46:37: [knifetop.smx] [KnifeTop] Error saving player (near "STEAM_0": syntax error)

How can i stopping this log spam?

[VJScope]

Originally Posted by pubhero Hi. I got many error messages / day from this plugin. See: L 01/17/2015 - 00:46:37: SourceMod error session started L 01/17/2015 - 00:46:37: Info (map "de_dust2") (file "errors_20150117.log") L 01/17/2015 - 00:46:37: [knifetop.smx] [KnifeTop] Error saving player (near "STEAM_0": syntax error) How can i stopping this log spam?

I'm not sure, but it might be because in csgo the first number in your steam id must be 1. At least when adding admins to your server, you have to change their STEAM_0.... to STEAM_1....

[pubhero]

Thank you for your answer, but i running CS:S server. I got sometimes the first error message, but now i have a new player and got another one too. The second error message presented only with this player and only with this name.

L 02/17/2015 - 15:50:09: [knifetop.smx] [KnifeTop] SQL_CreatePlayerCallback failure: unrecognized token: "'''''''''''\\ terminator //'''''''', current_timestamp)"

Maybe the SQL database can't handle some of these characters?
The author or some other programmer can repair these errors? Thanks in advance.

[3axap]

Some one know this:

Паша Шу�тров СУТУЛЯ

This is russian letter in base. MySQL base in utf8_general_ci. Plugin write wrong charset. In game too.
Some one know how i fix it? Thank you.