手机浏览 RSS 2.0 订阅 膘叔的简单人生 , 腾讯云RDS购买 | 超便宜Qcloud , 注册 | 登陆
浏览模式: 标准 | 列表2015年02月的文章

转:上海车牌拍卖技巧

活在上海的悲哀是车牌是要拍的,而且现在非上海籍的除了有人才引进居住证才能拍之外,其他的不能拍了(港澳台等请别BB,我是指正常的在上海打工的)

因为没拍过,所以先学习一下,从百度上copy了一个小经验来参考一下:http://jingyan.baidu.com/article/fdffd1f805de25f3e88ca140.html

方法/步骤

  1. 首先登陆国拍网,在十点半之前将车牌拍卖的软件下载好,输入账号密码,在十点半的时候在出价栏随便输入一个价格出价,表示你参加了拍卖。

  2. 然后你就可以随便喝杯茶什么的,

    接下来的到11点回来,大家先移动下拍牌界面 确保验证码弹出框不会挡住左边数据窗口。 

    然后不断刷验证码熟悉验证码的格式。

  3. 时间到了11点28分 这时请大家高度警惕 关闭所有联网软件 

    到十一点29分,最关键的时刻。

    这时主要策略有两种,一个是11点29分00秒在最高价上加600伏击,伏击成功之后马上再加300伏击;另外一个是11点29分20秒最高价加300伏击,伏击成功后马上再加300伏击 。

  4. 举例

    目前最低可成交价为44800,可修改区间为44500-45100,跟最低可成交价比上下300 。 加300伏击意思是在最高价45100基础上加300为45400,出价,输入好验证码,等待系统最高价到达45400的时候点击确定就算成功出价了 。 还有,在伏击阶段,大家是可以出价后把验证码先输好的,到最后点确定就可以了 。

  5. 以上是伏击法,

    拍牌结束后的十分钟后左边会出现拍牌结果的信息 若中标的话 恭喜了 !

     

 

希望是美好的,但能不能拍到,还是要看运气的。先备着,虽然这是几年前的东西了。现在都75000左右了!!!可以买辆车了,我晶啊

PS:http://jingyan.baidu.com/article/37bce2be347aee1002f3a294.html,这个网址更详细。

Tags: 车牌

What's the difference between utf8_general_ci and utf8_unicode_ci

Copy from http://stackoverflow.com/questions/766809/whats-the-difference-between-utf8-general-ci-and-utf8-unicode-ci

看到本文其实是源于Yii2 的migrate中的init,它其中就有一段:

PHP代码
  1. if ($this->db->driverName === 'mysql') {  
  2.     // http://stackoverflow.com/questions/766809/whats-the-difference-between-utf8-general-ci-and-utf8-unicode-ci  
  3.     $tableOptions = 'CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE=InnoDB';  
  4. }  

于是我才发现了上面的URL,然后打开看了下,发现是有人在提问:Between utf8_general_ci and utf8_unicode_ci, are there any differences in terms of performance?

然后有一个554个赞的评论,这样写:

There are at least two important differences:

  • Accuracy of sorting

    utf8_unicode_ci is based on the Unicode standard for sorting, and sorts accurately in a very wide range of languages.

    utf8_general_ci comes close to correct Unicode sorting in many common languages, but has a number of limitations: in some languages, it won't sort correctly at all. In others, it will merely have some quirks.

  • Performance

    utf8_general_ci is faster at comparisons and sorting, because it takes a bunch of performance-related shortcuts.

    utf8_unicode_ci uses a much more complex comparison algorithm which aims for correct sorting according in a very wide range of languages. This makes it slower to sort and compare large numbers of fields.

Unicode defines complex sets of rules for how characters should be sorted. These rules need to take into account language-specific conventions; not everybody sorts their characters in what we would call 'alphabetical order'.

  • As far as Latin (ie "European") languages go, there is not much difference between the Unicode sorting and the simplified utf8_general_ci sorting in MySQL, but there are still a few differences:

    For examples, the Unicode collation sorts "ß" like "ss", and "Œ" like "OE" as people using those characters would normally want, whereas utf8_general_ci sorts them as single characters (presumably like "s" and "e" respectively).

  • In non-latin languages, such as Asian languages or languages with different alphabets, there may be a lot more differences between Unicode sorting and the simplified utf8_general_ci sorting. The suitability of utf8_general_ci will depend heavily on the language used. For some languages, it'll be quite inadequate.

Some Unicode characters are defined as ignorable, which means they shouldn't count toward the sort order and the comparison should move on to the next character instead. utf8_unicode_ci handles these properly.

What should you use?

There is almost never any reason to use utf_general_ci anymore, as we have left behind the point where CPU speed is low enough that the performance difference would be important. Your database will almost certainly be limited by quite other bottlenecks than this nowadays. The difference in performance is only going to be measurable in extremely specialised situations, and if that's you, you'd already know about it. If you're experiencing slow sorting, in almost all cases it'll be an issue with your indexes/query plan. Changing your collation function should not be high on the list of things to troubleshoot.

When I originally wrote this answer (over 4 years ago) I said that if you wanted, you could use utf8_general_ci most of the time, and only use utf8_unicode_ci when sorting was going to be important enough to justify the performance cost. However, the performance cost is no longer really relevant (and it may not have been back then, either). It's more important to sort properly in whichever language your users are using.

One other thing I'll add is that even if you know your application only supports the English language, it may still need to deal with people's names, which can often contain characters used in other languages in which it is just as important to sort correctly. Using the Unicode rules for everything helps add peace of mind that the very smart Unicode people have worked very hard to make sorting work properly.

还有一些代码,不过我就不贴了,建议查看原网页,别说没地址。。

 

IOS下移除按钮原生样式 -webkit-appearance

如果你在ios的Safari下做过网页的预览你就会发现,它的button的效果是与你设计的完全不一样的,圆圆的效果,也不象PC上是方的,这是怎么回事?

原来,IOS环境下的按钮都是经过美化的,但通常我们在设计web app的时候不需要这些看上去老土的样式,所以,去除这些显得很有必要。

下面这句代码就是重置这些样式的:

CSS代码
  1. -webkit-appearance: none;  

因此,实际的代码就类似如下:

CSS代码
  1. input[type=button]{  
  2.     -webkit-appearance:none;  
  3.     outline:none  
  4. }  

可以试一下看看效果

又一个不错的UI皮肤

平时的工作中,除了bootstrap,其实还是有一些其他的皮肤是可以尝试的,比如这个“http://semantic-ui.com/”,你就可以看到与bootstrap等不同的效果。

semantic-ui准备了一些常用的小效果,而且自带了一些小皮肤,比如github的效果,比如bootstrap,twitter的小效果,你在使用中会发现它的好的

不多介绍,直接去官网看吧。如果你偷懒,就用这个链接下载吧:https://github.com/Semantic-Org/Semantic-UI/archive/1.10.2.zip

官网:http://semantic-ui.com/

github: https://github.com/semantic-org/semantic-ui/

Tags: semantic, bootstrap

Happy new year

羊年快乐。喜气羊羊,羊羊得意!

 
祝能看到我勃客的人在羊年里少出BUG,多出产品。皆大欢喜!
 
我自己的目标和愿望就不列出来了。也期望自己能够实现新年的愿望
Records:812