The first time I needed to have some kind of complex select statement, I started to pray about the ability to use regular expressions with mysql.
Easy as it may be: use REGEXP!
SELECT * FROM db.ip_addresses WHERE ip_address REGEXP '^192\.168\.0\.(133|135)$';
See the official documentation and details here.
Friday, 13 November 2009
mysql and regular expressions
Subscribe to: Post Comments (Atom)
About ICE negotiation
Disclaimer: I wrote this article on March 2022 while working with Subspace, and the original link is here: https://subspace.com/resources/i...
WebRTC applications use the ICE negotiation to discovery the best way to communicate with a remote party. I t dynamically finds a pair of...
On a previous post I shared my experiments with node.js as a WebSocket server. This is quite useful for people working on WebRTC prototyp...
Docker is an incredibly useful tool to build prototypes of Linux hosts and applications. You can easily build a network of servers inside...
hey! nice blog :) I've quit my weblogging activity, but I'm posting a lot on flickr :)ReplyDelete
Anyway, I think regexp is quite slow, perhaps ... where ip_address ='192.168.0.133' or ip_address='192.168.0.135'
is quicker if ip_address is indexed. Obviously, more complex regexp cannot be converted easily...
Thanks for your comment.ReplyDelete
Performance has been my first concern, although I haven't found so far a clear documentation on possible impacts.
Given that yes, it's probably not worth using a regexp for just 2 IP addresses, in my case the mysql statement is 'generated' by some other code and configuration files, so using that approach gives me the impression of higher flexibility.