 |
Houses and Rooms.zip (13,554 bytes) |
 |
crash actually in vkernel. |
 |
Actually you forgot to iterate cursor in the loop and you will get an endless loop staying on the first record. It must be something like this one: create or replace procedure test_enum_case ( ) begin declare v_cursor cursor for select * from houses; declare v_address string; declare v_house_type house_type; open v_cursor; fetch first v_cursor into v_address, v_house_type; loop begin case v_house_type when 'garden' then print v_address || ' - garden'; when 'ranch' then print v_address || ' - ranch'; when 'apartment' then print v_address || ' - apartment'; end case fetch NEXT v_cursor into v_address, v_house_type; EXCEPTION WHEN ERR_CURSOR_WRONG_POSITION THEN LEAVE end end loop end |
|
|
I had the cursor iteration in my project. I used this database to see if I could reproduce the issue and forgot to include the cursor iteration in the code. Also, are ENUMs and STRINGs interchangeable like DATEs and STRINGs? When I INSERT a new record, I use a string for an ENUM field and that works fine. However, when I used a CURSOR in a SQL procedure, I could not use a STRING variable for the ENUM field and had to use a variable that was declared as the ENUM type. I was able to work around the CASE issue that I had here by declaring another variable of type STRING and setting it to the value of the ENUM variable. I then used that STRING variable in my CASE statement. ----- For example (using the attached database): INSERT INTO houses(address, house_type) VALUES('123 Street', 'garden'); works fine. But, if the code I provided above is changed to declare v_house_type as STRING, there will be a crash at the FETCH statement. I had to change that v_house_type to house_type to avoid that crash. Then, I found the issue with the CASE statement. |
- Anonymous
