Converting !

I want to know how to Convert a LOTF Source that is .ini into a Non ini Source Any Guides? Tips, ty.

Co B,c,

.ini just saves the information into the folder, instead of into the database.

stay at mysql

inis wreck you acc if it has too much skills/profs

Do the hokey-pokey and learn to code.

Quote:

Originally Posted by ~Yuki~ stay at mysql inis wreck you acc if it has too much skills/profs

Rofl right ini class wont have any problems.

Dude, I would help you but I don't know how bro.

Quote:

Originally Posted by StarCurse Dude, I would help you but I don't know how bro.

Really useful..

@OP, just change the save and load system to MySQL. Just use some LOTF source and see how they did it. All you have to do is change the table names and maybe add some tables and / or delete some. It's easy, but might take a while.

Your going to have to get rid of the statements/functions that write to INI files, and replace them with statements/functions that write to a SQL (or whatever kind) of database you wish to use.

Because of how you worded your post, I'm going to assume you expect someone to do it for you (as in give you the code) which sadly is unlikely to happen.

@Smythe94 - Thanks ill take a look at that ;P

-----

@Tequila - ty too,

MySQL is Better than .ini files source....Trust me..i convert my PazeCO v3 (ini source) to Co: Paze v3 (MySQL Source)

I never said INI is gerneral bad i myselfe use ini atm coz i like to be able to edit in runtime

If you don't know how to edit a file at runtime you really shouldn't be calling yourself a programmer considering there is Win32 API functions to deal with INI files which can be harnessed into an easy-to-use wrapper-class.

In what sense is MySQL better than a flat-file system? You can't really just say "x" is better than "y" in this kind of case. With a flat-file system your less prone to have you system "hijacked", where as with a SQL-database, an attacker can generally find some way to SQL-inject and breach your database. This is just one example but the list goes on with SQL-languages winning some, and flat-files winning some.

Quote:

Originally Posted by _Tequila_ If you don't know how to edit a file at runtime you really shouldn't be calling yourself a programmer considering there is Win32 API functions to deal with INI files which can be harnessed into an easy-to-use wrapper-class. In what sense is MySQL better than a flat-file system? You can't really just say "x" is better than "y" in this kind of case. With a flat-file system your less prone to have you system "hijacked", where as with a SQL-database, an attacker can generally find some way to SQL-inject and breach your database. This is just one example but the list goes on with SQL-languages winning some, and flat-files winning some.

Lol, the only reason a few of the consider-themselves-smart people here say MySQL is better is because they either
1) Only listen to what they're told - Since sparkie will eat your face if you don't use a database system
2) Are retarded beyond reason like most

None of them have any real experience or testing done in the field of data management.

Well,
Thanks Alot Guys #Request Close

I Wount be needing this Anymore,