For or Against


“He that is not with me is against me” (Matt 12:30, Luke 11:23)

Those are strong words. They were spoken by Christ after casting out a devil and being accused by the Pharisees of doing it by the power of Beelzebub. And yet they are directly contradicted by Christ in his response to John’s concern about people who were casting out devils in the name of Christ but not directly following the apostles. “Forbid him not:”, he said, “for he that is not against us is for us.” (Luke 9:50, cf. Mark 9:40) Each of the two views is expressed twice:

“And Jesus said unto him, Forbid him not: for he that is not against us is for us.” (Luke 9:50)

“For he that is not against us is on our part.” (Mark 9:40; cf. Matt 18:7-35 & Luke 17:1-4)

“He that is not with me is against me: and he that gathereth not with me scattereth.” (Luke 11:23; cf. Matt 12:22-37, Mark 3:22-30, Luke 6:45; 12:10)

“He that is not with me is against me; and he that gathereth not with me scattereth abroad.” (Matt 12:30; cf. Mark 3:22-30, Luke 6:45; 11:14-26; 12:10)

I’ve looked a little for some explanation of the reversal. There’s at least one other instance in Christ’s ministry where he reverses his recommendations to the apostles. In Luke 9 (cf. Matt 10:5-10) he says:

“[2] And he sent them to preach the kingdom of God, and to heal the sick. [3] And he said unto them, Take nothing for your journey, neither staves, nor scrip, neither bread, neither money; neither have two coats apiece.”

This charge was reiterated in Luke 10, this time to the Seventy:

“[1] After these things the Lord appointed other seventy also, and sent them two and two before his face into every city and place, whither he himself would come. [2] Therefore said he unto them, The harvest truly is great, but the labourers are few: pray ye therefore the Lord of the harvest, that he would send forth labourers into his harvest. [3] Go your ways: behold, I send you forth as lambs among wolves. [4] Carry neither purse, nor scrip, nor shoes: and salute no man by the way.”

But by Luke 22 the situation has changed:

“[35] And he said unto them, When I sent you without purse, and scrip, and shoes, lacked ye any thing? And they said, Nothing. [36] Then said he unto them, But now, he that hath a purse, let him take it, and likewise his scrip: and he that hath no sword, let him sell his garment, and buy one.”

Maybe something similar happened between Luke 9 and Luke 11? Or perhaps the Book of Mormon settles the tie?



MySQL InnoDB tables vs. MyISAM tables


MySQL has multiple ways in which it can store your data, called storage engines. The two most commonly used engines are MyIASM and InnoDB; I have a hard time remembering which I wanted to use, and answering people when they ask why I used the type I did. So…

InnoDB tables support foreign keys; MyISAM does not. (ref)

“Full-text indexes can be used only with MyISAM tables”. (ref)

InnoDB supports transactions! Note autocommit is set by default. (ref)

Because MyISAM tables are non-transaction-safe they may be smaller, faster, and require less memory to update (ref).

The InnoDB engine also supports Clustered indexes, Data caches, and has finer locking granularity than MyISAM, although MyISAM does have something called “Geospatial indexing support.”

The official summaries:

MyISAM — The default MySQL storage engine and the one that is used the most in Web, data warehousing, and other application environments. MyISAM is supported in all MySQL configurations, and is the default storage engine unless you have configured MySQL to use a different one by default.

InnoDB — A transaction-safe (ACID compliant) storage engine for MySQL that has commit, rollback, and crash-recovery capabilities to protect user data. InnoDB row-level locking (without escalation to coarser granularity locks) and Oracle-style consistent non-locking reads increase multi-user concurrency and performance. InnoDB stores user data in clustered indexes to reduce I/O for common queries based on primary keys. To maintain data integrity, InnoDB also supports FOREIGN KEY referential-integrity constraints.


powered by WordPress     themed by Mukkamu     presented by ideaharbor.org     everything else by steve hulet