Quote: Originally Posted by
Moogly
How can you base it on Woodpecker? If you've never seen the source 8) maybe basing it on the IDEA of what woodpecker does, and no server can ever do it like woodpecker, and fyi woodpecker doesn't do it anyway like how you just described your method 8)
I have sent him Woodpecker.Storage.Database class. ;P
And I don't know what's up with you people above talking that this is 'useless' etc, well to be honest I have still coded Holograph more than any of you together, and I know where it's 'bugs' and 'weaknesses' are, and the database connection is one major weakness of it, that's why I spent alot of time on it in Woodpecker.
I appreciate the help from someone who also applies these changes in Holo a lot.
I've seen people's 'pooling implementations' before, but they were, as Cecer already said, nothing more than opening and closing the database connection for EVERY SINGLE QUERY, and then there's also no pooling at all since there are no 'Max Pool Size' parameters etc in the connection string.
To make a proper database system you have to rewrite all your queries, in Woodpecker it's like;
* create database object
* set parameters
* open connection
* execute queries
* execute queries
* and more queries
* close connection and dispose database object
If something like that has been done here too (or similar ofcourse), then thank you very much. =]
So goodluck with the testing etc!
- Nillus