在MySQL中isnull()函数不能作为替代null值!

MySQL中isnull()函数不能作为替代null值! 
如下: 
首先有个名字为business的表: 

SELECT ISNULL(business_name,'no business_name') AS bus_isnull FROM business WHERE id=2

直接运行就会报错:

错误代码: 1582

Incorrect parameter count in the call to native function 'isnull'

所以,isnull()函数在mysql中就行不通了。可以用ifnull()和coalesce()代替。如下: 
使用ifnull()函数:

SELECT IFNULL(business_name,'no business_name') AS bus_ifnull FROM business WHERE id=2

运行结果: 
 

 
当查询的值不为null时:

SELECT IFNULL(business_name,'no business_name') AS bus_ifnull FROM business WHERE id=1

结果如下: 
 

 
使用coalesce()函数:

SELECT COALESCE(business_name,'no business_name') AS bus_coalesce FROM business WHERE id=2

结果如下: 

 
当查询值不为null时:

SELECT COALESCE(business_name,'no business_name') AS bus_coalesce FROM business WHERE id=1

其中:coalesce()还可以返回第一个不为null的值。如下:

SELECT COALESCE(business_name,district_id,id) AS bus_coalesce FROM business WHERE id=2

那么,isnull()在mysql中怎么用呢?答案就是用在where后面。如下:

SELECT * FROM business WHERE ISNULL(business_name)

结果如下: 
 

 
同样,is null 和is not null 也是用在where后面。

SELECT * FROM business WHERE business_name IS NULL

结果如下: 

SELECT * FROM business WHERE business_name IS NOT NULL

                                                                                代码虐我千百遍。

                                                                                我待代码如初恋。

                                                                                哈哈哈

                                                                                

  • 3
    点赞
  • 8
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
Just like the other books I wrote, this one does not have a fixed scope. I did not start with an index. I didn't write a summary of each chapter in an attempt to define the scope. I do not do such things. There is only a high-level goal to explore continuous delivery and deployment inside Kubernetes clusters. What I did do, though, was to set a few guidelines. The first guideline is that all the examples will be tested on all major Kubernetes platforms. Well, that might be a bit far-fetched. I'm aware that any sentence that mentions "all" together with "Kubernetes" is bound to be incorrect. New platforms are popping out like mushrooms after rain. Still, what I can certainly do is to choose a few of the most commonly used ones. Minikube and Docker for Mac or Windows should undoubtedly be there for those who prefer to "play" with Docker locally. AWS is the biggest hosting provider so Kubernetes Operations (kops) must be included as well. Since it would be silly to cover only un-managed cloud, I had to include managed Kubernetes clusters as well. Google Kubernetes Engine (GKE) is the obvious choice. It is the most stable and features rich managed Kubernetes solution. Adding GKE to the mix means that Azure Container Service (AKS) and Amazon's Elastic Container Service (EKS) should be included as well so that we can have the "big trio" of the hosting vendors that offer managed Kubernetes. Unfortunately, even though AKS is available, it is, at this moment (June 2018), still too unstable and it's missing a lot of features. So, I'm forced to scale down from the trio to the GKE and EKS duo as representatives of managed Kubernetes we'll explore. Finally, a possible on-prem solution should be included as well. Since OpenShift shines in that area, the choice was relatively easy. All in all, I decided to test everything in minikube and Docker for Mac locally, AWS with kops as the representative of a cluster in the cloud, GKE for managed Kubernetes clusters, and OpenShift (

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值