DELIMITER $$
DROP PROCEDURE IF EXISTS eventsNearMe$$
CREATE PROCEDURE eventsNearMe(IN inIP VARCHAR(16))
BEGIN
DECLARE ipLAT FLOAT;
DECLARE ipLONG FLOAT;
SELECT iplocationdb_location.latitude, iplocationdb_location.longitude
INTO ipLAT, ipLONG
FROM `iplocationdb_ip`
LEFT JOIN iplocationdb_location ON iplocationdb_location.id=iplocationdb_ip.location_id
WHERE iplocationdb_ip.prefix=(INET_ATON(inIP)>>24)
AND INET_ATON(inIP) BETWEEN iplocationdb_ip.start_ip AND iplocationdb_ip.end_ip LIMIT 1;
CREATE TEMPORARY TABLE tempEVENTS
SELECT `eid`,(((acos(sin((ipLAT*pi()/180)) * sin((`lat`*pi()/180))+cos((ipLAT*pi()/180)) * cos((`lat`*pi()/180)) * cos(((ipLONG- `long`)*pi()/180))))*180/pi())*60*1.1515) as d FROM `mke_events` HAVING `d` <= 10 LIMIT 1;
SELECT * FROM tempEVENTS;
DROP TEMPORARY TABLE tempEVENTS;
END
$$
DELIMITER ;
The above code should, in my opinion, create a quick little sp to receive events near the given IP address. However, through all my searches, I did not find a satisfactory reason for throwing 1064 on DELIMITER (line 1).
Even if I have JUST:
DELIMITER $$
SELECT * FROM iplocationdb_location;
$$
DELIMITER ;
It still runs 1064. mySQL version 5.0.77.
NOTE. I have a space between DELIMITER and a delimited string. NOTE2: I use heidiSQL to run this script, which should be tantamount to running it from the command line as I understand it.
source
share