Subject: DocOz: Lean, Mean and trim by Memorial Day

From: Doc Oz <[email-masked]>
Date: Fri, 16 May 2014 11:31:39 -0700

Hey Atompub-archive,

It krept up on us.... Memorial Day, it's 11 days away.
And you havent lost those winter pounds that you want to yet. 

TV host and powerhouse DocOz has a way for you to drop ten lbs
before all the holiday BBQ's w/o working out

The best news, you can eat what you want at the Memorial Day party
and not gain the  back.

Sounds too good to be true? Its not....
Watch DocOz explain this miracle in a recent episode clip.

View DocOz Episode Clip Here: / http://www.awebeemum.com/docoz/fatmelting/episode/No509.video
[Episode No. 509]

-message settings - modify- Urgent Info Services 
/3205/ Lake Sarah/Independence, MN 55359 - http://www.awebeemum.com/skgh4/sknvik4.gnke4

Keep in mind that if the column is nullable, then null will be the value used for existing rows.   Richard Collette Jan 31 '12 at 15:431	  	RichardCollette what is nullable column. If my data type is int or varchar, it always takes null value for the existing rows even if I specify a default value. Does that mean the default value goes towards new records only?   Nick Feb 3 '12 at 15:04 @Thecrocodilehunter Nullable column means that you can insert Null for the columns value. If it's not a nullable column, you have to insert some value of that data type. So, for existing records, Null will be inserted in them and in new records, your default value will be inserted unless otherwise specified. Make sense?   Yatrix Feb 29 '12 at 16:42 I like this answer a little better than dbugger's because it explicitly names the default constraint. A default constraint is still created using dbugger's syntax, except its name is auto-generated. Knowing the exact name is handy when writing DROP-CREATE s
 cripts.   Walter Stabosz Mar 23 '12 at 12:43This is not correct. If you specify a default value using the DEFAULT constraint, it will be used as value for existing rows, at least in SQL Server 2008   Vertigo Jun 18 '12 at 11:04 @Vertigo That is ONLY true if the column is NOT NULL. Please try this: create table blah(a int not null primary key clustered); insert blah values (1), (2); alter table blah add b int null constraint df_blah_b default (0); select  from blah; You will see 2 NULL values for column b.   ErikE Jun 14 '13 at 22:19
 Alter the column to NOT NULL with a DEFAULT value. Then, with a second query, make the column nullable. Problem solved. 1st query adds your default values. 2nd allows allows nulls in the future.   Buttle Butkus Mar 26 at 20:20 outdated. That should be enough to know ;) It is not actively maintained anymore (and such)   KingCrunch Oct 12 '12 at 13:20 Bondye Oct 12 '12 at 13:58SDC: Please, don't use mysql_functions to write new code. They are no longer maintained and the community has begun deprecation process. See the red box? Instead you should learn about prepared statements and use either PDO or MySQLi. If you can't decide which, this article will help you. If you pick PDO, here is good tutorial. Also see Why shouldn't I use mysql functions in PHP?   Second Rikudo Oct 22 '12 at 18:11As of yesterday, the PHP dev team have now voted in favour of formally deprecating the mysql exension in PHP 5.This makes it more important to educate users not to use it. It may also be good to modify
  the answers here and/or the "standard comment message" we give to reflect this.   SDC Dec 10 '12 at 14:57@Calmarius: It's not using mysql itself that's faulty. I can write perfectly secure and robust code with mysql_too. The problem is that it promotes bad code. Newbies just use it without actually learning the precautions. And since it's deprecated now, we're better off without it for good.   Second Rikudo Jul 11 '13 at 9:43@MadaraUchiha The same newb@Calmarius: That's right. But the problem with mysqlis that most of the tutorials don't explain the gotchas, while most mysqli and PDO tutorials do.   Second Rikudo Jul 11 '13 at 12:34
Deprecated alone is reason enough to avoid them. They will not be there one day, and you will not be happy if you rely on them. The rest is just a list of things that using the old extensions has kept people from learning.   Tim Post Oct 12 '12 at 13:26
21	  	
Deprecation isn't the magic bullet everyone seems to think it is. PHP itself will not be there one day, yet we rely on the tools we have at our disposal today. When we have to change tools, we will.   Lightness Races in Orbit Dec 24 '12 at 14:29
25	  	
@LightnessRacesinOrbit  Deprecation isn't a magic bullet, it is a flag that says "We recognise this sucks so we aren't going to support it for much longer". While having better future proofing of code is a good reason to move away from the deprecated features, it isn't the only one (or even the main one). Change tools because there are better tools, not because you are forced to. (And changing tools before you are forced to means that you aren't learning the new ones just because your code has stopped working and needs fixing yesterday  which is the worst time to learn new tools).   Quentin Dec 24 '12 at 17:43
2@Quentin: Also correct :D   Lightness Races in Orbit Dec 26 '12 at 21:17
17	Lacking an OO interface is a non-argument in this discussion.Moving away from ext/mysql is not only about security, but also about having access to all the features of the MySQL databat/mysql was built for MySQL 3.23 and only got very few additions since then while mostly keeping compatibility with this old version which makes the code a bit harder to maintain. Missing features that is not supported by ext/mysql include:(from PHP manual)Stored procedures (can't handle multiple result sets)
Prepared statements
Encryption (SSL)
Compression
Full Charset support
Reason to not use MySql_* function

Not under active development
In deprecation process (so the intention is to remove it from a future version of PHP)
Lacks an OO interface
Doesn't support non-blocking, asynchronous queries
Doesn't support prepared statements or parametrized queries
Doesn't support stored procedures
Doesn't support multiple statements
Doesn't support transactions
Doesn't support all of the functionality in MySQL 5.1
Above point quoted from Quentin's answer

Lack of support for prepared statements is particularly important as they provide a clearer, less error prone method of escaping and quoting external data than manually escaping it with a separate function call.