<em>decode</em>的几种用法
1:使用<em>decode</em><em>判断</em>字符串是否一样
DECODE(value,if1,then1,if2,then2,if3,then3,...,else)
含义为
IF 条件=值1 THEN
RETURN(value 1)
ELSIF 条件=值2 THEN
RETURN(value 2)
......
ELSIF 条件=值n THEN
@SuppressWarnings("rawtypes") protected boolean isNull(Object o) { if (o == null) return true; boolean isNull = true; if (o instanceof List) { List t = (List) o; if (t != null &amp;&amp; !t....
Alright, so I'm implementing some push notifications in my app. I've written some PHP which should interact with a MySQL DB.
I want to store the device tokens in SQL as char(64) because I've come to believe this is good (I mean, it's supposed to be sent as binary later anyways).
On the iOS side I do this:
- (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken
{
NSString *tokenString = [deviceToken base64EncodedString];
NSDictionary *jsonDic = [NSDictionary dictionaryWithObjectsAndKeys:tokenString, @"Token", [NSNumber numberWithBool:YES], @"IsiDevice", [NSNumber numberWithBool:YES], @"Active", nil];
//... http request stuff
// what might be important is that the POST body is encoded as UTF8 (content-type set appropriately)
}
The base64 stuff comes from NSData+Base64 by Matt Gallagher. Now, on the PHP side, this happens:
// $tokenEncoded is exactly the same string as I sent from the app (type is string)
$tokenEncoded = $jsonData['Token'];
// $token becomes null! (type is string)
$token = base64_<em>decode</em>($tokenEncoded);
From php.net/manual on base64_<em>decode</em>'s return values:
Returns the original data or FALSE on failure. The returned data may be binary.
Now, I don't know more PHP then I've taught myself the last two days; but if the documentation says it should return FALSE or the original data, I find it very confusing that the returned value is a null-string (because I'm very sure the original data wasn't null!).
As the base64_<em>decode</em>d string becomes null, so does apparently my whole query string when I append it. That does not make for a very convincing query.
So my questions are, I guess: why does base64_<em>decode</em> return things it shouldn't? Once I actually get the data out of base64_<em>decode</em>, how should I include it in the query so that it is stored as I want it to in the DB (just append?)?
Additional info:
I'm using the Slim Framework. I'm doing all this in a route. $jsonData is taken from the body like such:
$jsonBody = Slim::getInstance()->request()->getBody();
$jsonData = json_<em>decode</em>($jsonBody, true);
Did some additional tests from the app, just to make sure nothing gets fudged up by my app's implementation of base 64:
DLOG(@"Device token as NSData: %@", deviceToken);
NSString *base64token = [deviceToken base64EncodedString];
DLOG(@"Device token as base64: %@", base64token);
DLOG(@"Device token back from base64: %@", [NSData dataFromBase64String:base64token]);
Output:
Device token as NSData: <65625f1c c33b9480 5a46f346 8b2877d0 95e92823 33e88e91 fd3a2abf febad972>
Device token as base64: ZWJfHMM7lIBaRvNGiyh30JXpKCMz6I6R/Toqv/662XI=
Device token back from base64: <65625f1c c33b9480 5a46f346 8b2877d0 95e92823 33e88e91 fd3a2abf febad972>
(
CASE
WHEN T2.BLESSNUM
IS NULL
THEN 0
ELSE T2.BLESSNUM
END) AS BLESSNUM
或者
ENCODE( T2.BLESSNUM， NULL，0，T2.BLESSNUM） AS BLESSNUM
ENCODE(t.status,'C','审批通过','P','审批中'
情况一:
select (case when trim(' ') is not null then 'not null' else 'is null' end) as age from dual;
输出结果：age： 'is null'
情况二:删除trim()
select (case when ' ' is not null the
IF p_Gold_Card_No
p_Audit_Rst_Flag := 'Y';
p_Rcd_Audit_Item.Audit_Rst_Flag := p_Audit_Rst_Flag;
RETURN;
END IF;
上述写法是错误的，正确的写法是：
IF p_Gold_Card_No is not nu
null只能通过is null 或者 is not null 来<em>判断</em>,其他操作符与null操作都是false.
select * from table where col = null (错误的,查不出正确的结果)
select * from table where col is null (正确的)
select vcityarea 所属区 from zbdl_company select vcityarea 所属区 from zbdl_company where vcityarea like '%'查询出<em>空</em>字段与<em>非</em><em>空</em>字段select vcityarea 所属区 from zbdl_company where nvl (vcityarea,'null')...
首先跟大家说明一点，我们做 IT 类的外包开发，是<em>非</em>标品开发，所以很有可能在开发过程中会有这样那样的需求修改，而这种需求修改很容易造成扯皮，进而影响到费用支付，甚至出现做完了项目收不到钱的情况。
那么，怎么保证自己的薪酬安全呢？
我们在开工前，一定要做好一些证据方面的准备（也就是“讨薪”的理论依据），这其中最重要的就是需求文档和验收标准。一定要让需求方提供这两个文档资料作为开发的基础。之后开发...
从 PC 时代至今，众人只知在 CPU、GPU、XPU、制程、工艺等战场中，英特尔在与同行硬件芯片制造商们的竞争中杀出重围，且在不断的成长进化中，成为全球知名的半导体公司。殊不知，在「刚硬」的背后，英特尔「柔性」的软件早已经做到了全方位的支持与支撑，并持续发挥独特的生态价值，推动产业合作共赢。 而对于这一不知人知的 B 面，很多人将其称之为英特尔隐形的翅膀，虽低调，但是影响力却不容小觑。
那么，在...
Idon’t know what that dream is that you have, I don't care how disappointing it might have been as you've been working toward that dream,but that dream that you’re holding in your mind, that it’s po...
