In my Opinion, even if MariaDB and MySQL are nearly the same, I think there should be a version of TOAD specifically called "TOAD for MariaDB" (Even if it is only a name change). I just received an e-mail a few days ago saying that "TOAD for PostgreSQL" is going to be released, having "TOAD for MariaDB" would also be great. Thank you. Juan
↧
Forum Post: RE: Will Toad for Mysql support in the future MariaDB
↧
Forum Post: RE: Can not open SQL files while connected
Please download this build and try. http://community-downloads.quest.com/toadsoft/tda/ToadforMySQL_Freeware_8.0.0.229.zip If this still hangs, then when it is hanging go to the task manager, right click and generate a dump file. Try attaching to this thread. It might be too large and you might have to use drop box or something.
↧
↧
Forum Post: Trouble getting database into subversion version control
I'm trying to get a database into version control and all the database objects are showing a status of "uninitialized". I think I must be missing a step, but there doesn't seem a way to commit, check in, or check out anything to get it into version control. The Perspective screen doesn't list any objects. Running Toad for MySQL 7.9.0.637 and svn version 1.9.5.1210. Connections to the repository with this version work fine, the "Try Login" on the version control configuration screen returns the green check mark. Let me know if anybody has ideas for resolution. Thanks Seth
↧
Forum Post: RE: Trouble getting database into subversion version control
Hi Seth, this issue usually happen when Toad is not able get status of object. I expect that you have DB access to tables you want to add to your VC (mean you are able get DDL script) so probalem have to by on SVN side. At first you have to be sure that you have user which is able update your working folder and you have OS rights to write there. Sometimes there should be an issue when user choose some system folder for repository (like C:\ or Desktop). You can also check if Toad created ToadSetting in your working folder. There have to be XML setting if you did Version Control Wizard successfully. As a last thing you can try remove App Data from Toad for Version Control so we will be sure we are working with current data. You will find this folder in "C:\Users\ \AppData\Roaming\Quest Softwar\ \Version Control". I tested MySQL DB and same Subversion version without problem. Let me know if it hepls or not. Filip
↧
Forum Post: RE: Will Toad for Mysql support in the future MariaDB
I believe this to be a windows installer issue, as it's an error reported in the MS support forums for Office too (see https://support.microsoft.com/en-us/help/907342/you-receive-an-this-action-is-only-valid-for-products-that-are-currently-installed-error-message-when-you-try-to-start-an-office-program ). Looking at your screen-shot I notice you are running the installer from a network drive - I've had experience of installation failures from a network drive previously, so I'd try copying the install file to a local drive and running the installation from there. I've used Toad for mysql on a Windows PC with the latest version of Xampp (where MariaDB is the substitute for MySQL) and it works fine.
↧
↧
Forum Post: Error by debugging stored procedure on MariaDB 10.2
Hi Toad, Today I tried to debug a stored procedure on MariaDB. There comes up a database error whch shows me that the internal code (automatically created by toad before debugging starts) fails. I copied the code into a text editor and found out what happened. The corresponding lines are marked red and boled. --> begin of my code CREATE PROCEDURE questdebug.6c476170dc7e0dcd5b6c762c6a92138ab54df03fimpl(IN p_id BIGINT, IN p_level INT(4), IN p_url VARCHAR(512), IN p_process_flag INT(2), IN p_home_id BIGINT, OUT p_return BIGINT) BEGIN DECLARE v_error TINYINT DEFAULT 0; DECLARE v_error_message VARCHAR(512); BEGIN DECLARE EXIT HANDLER FOR SQLEXCEPTION BEGIN GET DIAGNOSTICS CONDITION 1 @sqlstate = RETURNED_SQLSTATE, @errno = MYSQL_ERRNO, @text = MESSAGE_TEXT; IF @errno = 1062 THEN # duplicate key -> go ahead SET v_error_message = CONCAT('WARNING ', @errno, ' (', @sqlstate, '): ', @text); CALL crawler.p_create_url_log(p_id, 'PROCEDURE', 'p_create_url_pages', v_error_message, CURRENT_TIMESTAMP(6), @out_return); SET p_return = 0; ELSE -- -------------- -- logging error -- -------------- SET v_error_message = CONCAT('ERROR ', @errno, ' (', @sqlstate, '): ', @text); CALL crawler.p_create_url_log(p_id, 'PROCEDURE', 'p_create_url_pages', v_error_message, CURRENT_TIMESTAMP(6), @out_return); SET p_return = p_id; CALL questsoftware.DEBUGSET('p_id','P',p_id); CALL questsoftware.DEBUGSET('p_level','P',p_level); CALL questsoftware.DEBUGSET('p_url','P',p_url); CALL questsoftware.DEBUGSET('p_process_flag','P',p_process_flag); CALL questsoftware.DEBUGSET('p_home_id','P',p_home_id); CALL questsoftware.DEBUGSET('p_return','P',p_return); CALL questsoftware.DEBUGSET('v_error','L',v_error); CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message); CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_pages',30); END IF; CALL questsoftware.DEBUGSET('p_id','P',p_id); CALL questsoftware.DEBUGSET('p_level','P',p_level); CALL questsoftware.DEBUGSET('p_url','P',p_url); CALL questsoftware.DEBUGSET('p_process_flag','P',p_process_flag); CALL questsoftware.DEBUGSET('p_home_id','P',p_home_id); CALL questsoftware.DEBUGSET('p_return','P',p_return); CALL questsoftware.DEBUGSET('v_error','L',v_error); CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message); CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_pages',31); END CALL questsoftware.DEBUGSET('p_id','P',p_id); CALL questsoftware.DEBUGSET('p_level','P',p_level); CALL questsoftware.DEBUGSET('p_url','P',p_url); CALL questsoftware.DEBUGSET('p_process_flag','P',p_process_flag); CALL questsoftware.DEBUGSET('p_home_id','P',p_home_id); CALL questsoftware.DEBUGSET('p_return','P',p_return); CALL questsoftware.DEBUGSET('v_error','L',v_error); CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message); CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_pages',31) ;; # initialize return code SET p_return = 0; --> end of my code The END statement is the END of my DECLARE EXIT HANDLER ..... normally it ends with a ';' -> but here the apostrophe is missing. But in my source it is available. I have seent that the debug code was moved directly behind the END, so the last line of the Debug code ends with an double apostrophe ';;'. This causes the error and I found no solution to handle this error. By the way: Without debugging the procedure runs without error. Hopefully you can solve the error into the next release. Your software is great. Thanks. Kind regards Michael Here is the original code from error message: CREATE PROCEDURE questdebug.6c476170dc7e0dcd5b6c762c6a92138ab54df03fimpl(IN p_id BIGINT, IN p_level INT(4), IN p_url VARCHAR(512), IN p_process_flag INT(2), IN p_home_id BIGINT, OUT p_return BIGINT) BEGIN DECLARE v_error TINYINT DEFAULT 0; DECLARE v_error_message VARCHAR(512); BEGIN DECLARE EXIT HANDLER FOR SQLEXCEPTION BEGIN GET DIAGNOSTICS CONDITION 1 @sqlstate = RETURNED_SQLSTATE, @errno = MYSQL_ERRNO, @text = MESSAGE_TEXT; IF @errno = 1062 THEN # duplicate key -> go ahead SET v_error_message = CONCAT('WARNING ', @errno, ' (', @sqlstate, '): ', @text); CALL crawler.p_create_url_log(p_id, 'PROCEDURE', 'p_create_url_pages', v_error_message, CURRENT_TIMESTAMP(6), @out_return); SET p_return = 0; ELSE -- -------------- -- logging error -- -------------- SET v_error_message = CONCAT('ERROR ', @errno, ' (', @sqlstate, '): ', @text); CALL crawler.p_create_url_log(p_id, 'PROCEDURE', 'p_create_url_pages', v_error_message, CURRENT_TIMESTAMP(6), @out_return); SET p_return = p_id; CALL questsoftware.DEBUGSET('p_id','P',p_id);CALL questsoftware.DEBUGSET('p_level','P',p_level);CALL questsoftware.DEBUGSET('p_url','P',p_url);CALL questsoftware.DEBUGSET('p_process_flag','P',p_process_flag);CALL questsoftware.DEBUGSET('p_home_id','P',p_home_id);CALL questsoftware.DEBUGSET('p_return','P',p_return);CALL questsoftware.DEBUGSET('v_error','L',v_error);CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message);CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_pages',30);END IF; CALL questsoftware.DEBUGSET('p_id','P',p_id);CALL questsoftware.DEBUGSET('p_level','P',p_level);CALL questsoftware.DEBUGSET('p_url','P',p_url);CALL questsoftware.DEBUGSET('p_process_flag','P',p_process_flag);CALL questsoftware.DEBUGSET('p_home_id','P',p_home_id);CALL questsoftware.DEBUGSET('p_return','P',p_return);CALL questsoftware.DEBUGSET('v_error','L',v_error);CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message);CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_pages',31);ENDCALL questsoftware.DEBUGSET('p_id','P',p_id);CALL questsoftware.DEBUGSET('p_level','P',p_level);CALL questsoftware.DEBUGSET('p_url','P',p_url);CALL questsoftware.DEBUGSET('p_process_flag','P',p_process_flag);CALL questsoftware.DEBUGSET('p_home_id','P',p_home_id);CALL questsoftware.DEBUGSET('p_return','P',p_return);CALL questsoftware.DEBUGSET('v_error','L',v_error);CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message);CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_pages',31);; # initialize return code SET p_return = 0; -- ------------- -- insert record -- ------------- CALL questsoftware.DEBUGSET('p_return','P',p_return);CALL questsoftware.DEBUGSET('p_id','P',p_id);CALL questsoftware.DEBUGSET('p_level','P',p_level);CALL questsoftware.DEBUGSET('p_url','P',p_url);CALL questsoftware.DEBUGSET('p_process_flag','P',p_process_flag);CALL questsoftware.DEBUGSET('p_home_id','P',p_home_id);CALL questsoftware.DEBUGSET('v_error','L',v_error);CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message);CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_pages',39);INSERT INTO crawler.t_url_pages(id, url_level, url, process_flag, id_home_url) VALUES (p_id, p_level, p_url, p_process_flag, p_home_id); CALL questsoftware.DEBUGSET('p_id','P',p_id);CALL questsoftware.DEBUGSET('p_level','P',p_level);CALL questsoftware.DEBUGSET('p_url','P',p_url);CALL questsoftware.DEBUGSET('p_process_flag','P',p_process_flag);CALL questsoftware.DEBUGSET('p_home_id','P',p_home_id);CALL questsoftware.DEBUGSET('p_return','P',p_return);CALL questsoftware.DEBUGSET('v_error','L',v_error);CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message);CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_pages',40);END; CALL questsoftware.DEBUGSET('p_id','P',p_id);CALL questsoftware.DEBUGSET('p_level','P',p_level);CALL questsoftware.DEBUGSET('p_url','P',p_url);CALL questsoftware.DEBUGSET('p_process_flag','P',p_process_flag);CALL questsoftware.DEBUGSET('p_home_id','P',p_home_id);CALL questsoftware.DEBUGSET('p_return','P',p_return);CALL questsoftware.DEBUGSET('v_error','L',v_error);CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message);CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_pages',42);END;
↧
Forum Post: RE: Trouble getting database into subversion version control
I installed 8.0.0.279 and got the same result. All the database objects show as uninitialized. The ToadSettings folder gets created along with the ...toadvc.xml file. Seth Walter Senior Database Developer, Nutmeg Consulting P 860.256.4822 x714 | F 866.622.9487 | E seth@nutmegit.com
↧
Forum Post: JSON support in TmSQL / Latest Beta
Is there an update on https://www.toadworld.com/products/toad-for-mysql/f/22/t/31142 i.e. JSON data type support in Toad ? I required this support and searched on the forums. From post https://www.toadworld.com/products/toad-for-mysql/f/22/p/31978/64241#64241 identified link http://community-downloads.quest.com/toadsoft/MySQL/ToadForMySQL_Beta_8.0.0.495.zip Tried installing this but it fails with an installer option to choose "Uninstall Toad for MySQL beta and continue with install" and "Uninstall Toad for MySQL beta only" required. Tried both neither works. Funnily have never installed Beta earlier. So uninstalled existing Toad for MySQL still the installer didn't allow me to proceed throwing up the same screen. After a bit of searching got this link https://www.toadworld.com/m/freeware/1612/download to register and download a new installer Unfortunately India is not listed in the country options hence unable to download. Any suggestions ? I am able to work using MySQL Community Workbench but would much rather Prefer TmSQL Thanks Mohan
↧
Forum Post: RE: Trouble getting database into subversion version control
Hi, from your log file I see problem with loading some DB objects. Is it possible that you have more objects with same name? I created task for fix QAT-10615 but because we are not able reproduce it there is not any easy solution. Filip
↧
↧
Forum Post: RE: Error by debugging stored procedure on MariaDB 10.1
Hi, I have tested again. It looks like that the own statements inserted by TOAD in the DECLARE statement does ignore the ending semicolon and puts the own statements betweeen the END statement and the semicolon. Is there anyone who can reproduce this issue and can provide a solution? Kind regards Michael CREATE PROCEDURE questdebug.f7c083896cd6be6cab48a11b9cd2ca17cb2a0294impl(IN p_id BIGINT, IN p_level INT(4), IN p_source LONGTEXT, IN p_tag_id INT(11), OUT p_return BIGINT) BEGIN DECLARE v_error TINYINT DEFAULT 0; DECLARE v_error_message VARCHAR(100 )C ALL questsoftware.DEBUGSET('p_id','P',p_id);CALL questsoftware.DEBUGSET('p_level','P',p_level);CALL questsoftware.DEBUGSET('p_source','P',p_source);CALL questsoftware.DEBUGSET('p_tag_id','P',p_tag_id);CALL questsoftware.DEBUGSET('p_return','P',p_return);CALL questsoftware.DEBUGSET('v_error','L',v_error);CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message);CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_footer',10) ;; # initialize return code SET p_return = 0; -- ------------- -- insert record -- ------------- CALL questsoftware.DEBUGSET('p_return','P',p_return);CALL questsoftware.DEBUGSET('p_id','P',p_id);CALL questsoftware.DEBUGSET('p_level','P',p_level);CALL questsoftware.DEBUGSET('p_source','P',p_source);CALL questsoftware.DEBUGSET('p_tag_id','P',p_tag_id);CALL questsoftware.DEBUGSET('v_error','L',v_error);CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message);CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_footer',20);INSERT INTO crawler.t_url_footer(id, url_level, `source`, tag_id) VALUES (p_id, p_level, p_source, p_tag_id); CALL questsoftware.DEBUGSET('p_id','P',p_id);CALL questsoftware.DEBUGSET('p_level','P',p_level);CALL questsoftware.DEBUGSET('p_source','P',p_source);CALL questsoftware.DEBUGSET('p_tag_id','P',p_tag_id);CALL questsoftware.DEBUGSET('p_return','P',p_return);CALL questsoftware.DEBUGSET('v_error','L',v_error);CALL questsoftware.DEBUGSET('v_error_message','L',v_error_message);CALL questsoftware.DEBUGTRACE('PROCEDURE','crawler','p_create_url_footer',22);END;
↧
Forum Post: RE: Run .sql file from editor
Thanks for the reply. Gave this a shot, but Toad says: MySQL Database Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SOURCE C:\test\test01.sql' at line 1 I tried it as: SOURCE "C:\test\test01.sql" and as: SOURCE C:\test\test01.sql But no luck either way. Any other ideas?
↧
Forum Post: RE: Run .sql file from editor
What is the message you are getting from TOAD / MySQL?
↧
Forum Post: RE: Run .sql file from editor
Another option is to just simply open the .sql file in the editor and run it. Pressing F5 or look for the 'Execute scripts' button on the toolbar (a green right arrow).
↧
↧
Forum Post: RE: Trouble getting database into subversion version control
I installed that version of Toad Data Point and it did not have any impact. Did you send the correct link? I figured there might be shared components between Toad for MySQL and data point? Seth Walter Senior Database Developer, Nutmeg Consulting P 860.256.4822 x714 | F 866.622.9487 | E seth@nutmegit.com
↧
Forum Post: RE: Trouble getting database into subversion version control
Geese! You would think I was blonde! Woops, I am[H] community-downloads.quest.com/.../ToadforMySQL_Freeware_8.0.0.284.zip
↧
Forum Post: RE: Trouble getting database into subversion version control
The .284 zip file has the same .279 exe in it. Is there a self service way to search and get the latest file? I couldn't find any on the website. Seth Walter Senior Database Developer, Nutmeg Consulting P 860.256.4822 x714 | F 866.622.9487 | E seth@nutmegit.com
↧
Forum Post: RE: Object reference not set to an instance of an object error while exporting data to SQL query in Toad for MySQL 7.9.0.637
Try this build. http://community-downloads.quest.com/toadsoft/tda/ToadDataPoint_pro_4.2.0.283.x64.zip
↧
↧
Wiki Page: [고고티켓] 1800-4840 go1800 휴대폰결제현금 모바일결제현금 핸드폰결제현금
고고티켓 1800-4840 go1800 모바일상품권매입 문화상품권매입 모바일상품권현금화 문화상품권현금화 고고티켓만의 자신감 1800-4840 go1800 1. 고객만족 1위업체 고고티켓!! 2. 재방문 1위업체 고고티켓!! 3. 지인소개 1위업체 고고티켓!! 안전한 거래를 찾으신가요 고고티켓으로 고고!! 친절한 상담을 원하시나요 고고티켓으로 고고!! 언제나 고객님에게 최선을 다하는 안전한거래 친절한상담 신속한처리를 위해 노력하겠습니다 고고티켓 서비스 1800-4840 go1800 1. 모바일상품권매입 & 모바일상품권현금화 2. 문화상품권매입 & 문화상품권현금화 3. 휴대폰결제현금화 & 핸드폰결제현금화 고고티켓만의 추가혜택 1800-4840 go1800 1. 20만원당 상품권경우 추가혜택!! 2. 20만원당 휴대폰결제경우 추가혜택!! 고고티켓 상품권매입 상품권현금화 상품권현금교환 모바일상품권매입 모바일상품권현금화 문화상품권매입 문화상품권현금화 문상매입 문상현금화 해피머니상품권매입 해피머니상품권현금화 도서상품권매입 도서상품권현금화 소액결제현금화 소액결제 휴대폰결제 핸드폰결제 휴대폰소액결제 핸드폰소액결제 휴대폰결제현금화 핸드폰결제현금화 휴대폰소액결제현금화 핸드폰소액결제현금화 구글결제 구글결제현금화 드라마무료다시보기 파워볼 #고고티켓 #상품권매입 #상품권현금화 #상품권현금교환 #모바일상품권매입 #모바일상품권현금화 #문화상품권매입 #문화상품권현금화 #문상매입 #문상현금화 #해피머니상품권매입 #해피머니상품권현금화 #도서상품권매입 #도서상품권현금화 #소액결제현금화 #소액결제 #휴대폰결제 #핸드폰결제 #휴대폰소액결제 #핸드폰소액결제 #휴대폰결제현금화 #핸드폰결제현금화 #휴대폰소액결제현금화 #핸드폰소액결제현금화 #구글결제 #구글결제현금화 #드라마무료다시보기 #파워볼
↧
Wiki Page: [고고티켓] 1800-4840 go1800 휴대폰결제현금화 모바일결제현금화 핸드폰결제현금화
고고티켓 1800-4840 go1800 모바일상품권매입 문화상품권매입 모바일상품권현금화 문화상품권현금화 고고티켓만의 자신감 1800-4840 go1800 1. 고객만족 1위업체 고고티켓!! 2. 재방문 1위업체 고고티켓!! 3. 지인소개 1위업체 고고티켓!! 안전한 거래를 찾으신가요 고고티켓으로 고고!! 친절한 상담을 원하시나요 고고티켓으로 고고!! 언제나 고객님에게 최선을 다하는 안전한거래 친절한상담 신속한처리를 위해 노력하겠습니다 고고티켓 서비스 1800-4840 go1800 1. 모바일상품권매입 & 모바일상품권현금화 2. 문화상품권매입 & 문화상품권현금화 3. 휴대폰결제현금화 & 핸드폰결제현금화 고고티켓만의 추가혜택 1800-4840 go1800 1. 20만원당 상품권경우 추가혜택!! 2. 20만원당 휴대폰결제경우 추가혜택!! 고고티켓 상품권매입 상품권현금화 상품권현금교환 모바일상품권매입 모바일상품권현금화 문화상품권매입 문화상품권현금화 문상매입 문상현금화 해피머니상품권매입 해피머니상품권현금화 도서상품권매입 도서상품권현금화 소액결제현금화 소액결제 휴대폰결제 핸드폰결제 휴대폰소액결제 핸드폰소액결제 휴대폰결제현금화 핸드폰결제현금화 휴대폰소액결제현금화 핸드폰소액결제현금화 구글결제 구글결제현금화 드라마무료다시보기 파워볼 #고고티켓 #상품권매입 #상품권현금화 #상품권현금교환 #모바일상품권매입 #모바일상품권현금화 #문화상품권매입 #문화상품권현금화 #문상매입 #문상현금화 #해피머니상품권매입 #해피머니상품권현금화 #도서상품권매입 #도서상품권현금화 #소액결제현금화 #소액결제 #휴대폰결제 #핸드폰결제 #휴대폰소액결제 #핸드폰소액결제 #휴대폰결제현금화 #핸드폰결제현금화 #휴대폰소액결제현금화 #핸드폰소액결제현금화 #구글결제 #구글결제현금화 #드라마무료다시보기 #파워볼
↧
Wiki Page: [고고티켓] 1800-4840 go1800 모바일소액결제현금 휴대폰소액결제현금 핸드폰소액결제현금
고고티켓 1800-4840 go1800 모바일상품권매입 문화상품권매입 모바일상품권현금화 문화상품권현금화 고고티켓만의 자신감 1800-4840 go1800 1. 고객만족 1위업체 고고티켓!! 2. 재방문 1위업체 고고티켓!! 3. 지인소개 1위업체 고고티켓!! 안전한 거래를 찾으신가요 고고티켓으로 고고!! 친절한 상담을 원하시나요 고고티켓으로 고고!! 언제나 고객님에게 최선을 다하는 안전한거래 친절한상담 신속한처리를 위해 노력하겠습니다 고고티켓 서비스 1800-4840 go1800 1. 모바일상품권매입 & 모바일상품권현금화 2. 문화상품권매입 & 문화상품권현금화 3. 휴대폰결제현금화 & 핸드폰결제현금화 고고티켓만의 추가혜택 1800-4840 go1800 1. 20만원당 상품권경우 추가혜택!! 2. 20만원당 휴대폰결제경우 추가혜택!! 고고티켓 상품권매입 상품권현금화 상품권현금교환 모바일상품권매입 모바일상품권현금화 문화상품권매입 문화상품권현금화 문상매입 문상현금화 해피머니상품권매입 해피머니상품권현금화 도서상품권매입 도서상품권현금화 소액결제현금화 소액결제 휴대폰결제 핸드폰결제 휴대폰소액결제 핸드폰소액결제 휴대폰결제현금화 핸드폰결제현금화 휴대폰소액결제현금화 핸드폰소액결제현금화 구글결제 구글결제현금화 드라마무료다시보기 파워볼 #고고티켓 #상품권매입 #상품권현금화 #상품권현금교환 #모바일상품권매입 #모바일상품권현금화 #문화상품권매입 #문화상품권현금화 #문상매입 #문상현금화 #해피머니상품권매입 #해피머니상품권현금화 #도서상품권매입 #도서상품권현금화 #소액결제현금화 #소액결제 #휴대폰결제 #핸드폰결제 #휴대폰소액결제 #핸드폰소액결제 #휴대폰결제현금화 #핸드폰결제현금화 #휴대폰소액결제현금화 #핸드폰소액결제현금화 #구글결제 #구글결제현금화 #드라마무료다시보기 #파워볼
↧