New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
<?=$secret==1?"This is NOT secret, whink, whink":""?>
/troll
lol I couldn't stop laughing, his thanks are in a group other than the rest, means he is probably still banned, but he can still participate by thanking but not posting, that's just funny
it is it's signature you fool >.>
@ VMPort: I guess I know a versed programmer works in php and web design as well (you might need for the programmer to your requirement for GUI), he's also 1-Does really fast work. 2-Gets a small hourly fee and overall isn't greedy. And he's from Canada I guess. (if you actually hired him, project was finished, plus you are satisfied, will I get a sort of reward then? )
O_o Sorry. I just thought it was his soul
Also, you put = instead of ==
Damn. It was just form my head with a los of works, I hate you now.. well, please first send me the code of the blog and then I will hate you
And the fool it was j/k, too. don't take it seriously!
Heres the page controller, I hope you realise how basic it actually is
It was just fine
@VMPort: I've PM'd you his info.
Ideally you would not use the closing "?>" tag, as well. My (personal) preference would have been, though:
Nice, without MySQL it seems how about a PHP that reads the "node" directory to know how many posts are they? Seems a very good project!
Since the blog script is just.... one script, only the blog node actually starts the database, its not system wide.
And as I said, its very minimal and small, but bloody quick.
and where did you get the rich-text editor?
What rich-text editor?
http://nicedit.com/
that, thanks.
Damn naruto, stop thanking all @Daniel posts!
@Daniel you should convert your scripts to either use PDO or MySQLi. Here's the main #1 reason:
http://news.php.net/php.internals/53799
In your __construct functons you do not need your variables in quotes. Not sure why you did that. Here's your class, rewritten to use PDO, also:
As a plus, this should (mostly, except for the getTable function) work with your existing code. For a bonus: If you changed how you __constructed this, you can easily change to a SQLite database, or any other DSN you want!. Wait, theres more! You have access to the PDO functions.
@Debug I've never used PDO or MySQLi.
From what I can see of your rape to my code, PDO makes fetching stuff so much easier?
I think he has a secret crush on me
What people seem to constantly miss is that that post is not an announcement saying that mysql_ is deprecated (which it is not, for the record), but a proposal on educating users. It does not actually state any reasons for switching to PDO, nor does it claim deprecation.
Alright lets try to bring this back on track for Ash
I'll keep an eye on IRC for anyone that's a skilled coder and looking for work.
Francisco
1) It's more future proof (mysql_* functions as you read are slowly being deprecated.)
2) You're not tied to just mysql, for example you can use SQLite
3) Was introduced in PHP 2.0, and currently only receives updates for maintenance. (http://php.net/manual/en/mysqlinfo.api.choosing.php)
4) No MySQL 5.1+ functionality.
Hell, look at this page
http://php.net/manual/en/intro.mysql.php
"This extension is not recommended for writing new code. Instead, either the mysqli or PDO_MySQL extension should be used. See also the MySQL API Overview for further help while choosing a MySQL API."
I'm sorry if you see that as a rape of your code. To be fair, not much has changed, other than using objects other than functions. If you like functions, however, you can gladly use the mysqli_* functions.
@Fran: Yup, I agree. Sorry
@joepie91
Still mysql_* functions are being discouraged. Isn't that some thing? Notice any major PHP 5.3+ (or any code done in the past year) has most likely been done in PDO or MySQLi. Also
As anyone knows how long it takes for the PHP team to deprecate anything, it's better to warn off new-comers from using the mysql_ functions. Same is what I'm doing right now, warning off others from using the mysql_* functions.
Claims for deprecation: "- Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0"
Also (I'm really rambling now, sorry), but it does state reasons for PDO, specifically, "with PDO being the PHP way and main focus of future endeavors".
I have had a positive experience hiring developers off Elance.com so you might want to consider posting a job there
Thank you all for your input, i think we have found our man
It's a proposal on a mailing list, not an announcement or claim.