| Summary: | postresql syntax highlighting error | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | andreaswuest |
| Component: | syntax | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | christoph, me |
| Priority: | NOR | Keywords: | investigated, triaged |
| Version First Reported In: | 2.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
The text after the COPY command is *not* valid SQL. It seems like the idea is that if pgsql encounters the command, it simulates reading from STDIN untill some delimiter string is seen. Or, if you feed your file directly into the STDIN of a pgsql client app, that text isn't SQL either, just text. To get the highlighter to deal with that, you need to treat that exact command special (COPY) so that if the command ends in a FROM clause with the value "stdin" you go to a context that will end when the delimiter is seen. I add the author of the pgsql highlight. If you want help fixing this, visit #kate at irc.freenode.net. Btw, the pgsql highlight seems to have no licence. make this a wish Won't be fixed, if nobody provides a patch, sorry. kate-editor.org for information about to write hl. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
Version: 2.2.1 (using KDE KDE 3.2.3) Installed from: Gentoo Packages OS: Linux Hi, syntax highlighting is broken for postgresql .sql scripts that contain single ' characters in a string. i am using postgresql 7.3.6 and created the following valid dump from my database. problem is that the code between the "COPY teams (teamid, name) FROM stdin;" and the end mark "\." must not be highlighted (ignored), since it is no sql code. if there is an uneven number of "'" (as in "Borussia M'gladbach") character in that non sql code, the syntax highlighting for the following sql code is broken (everything following the ' character is red). if there is an even number of "'" in that code, only the code between the "'" characters is red. just try it. best regards, Andreas -- -- PostgreSQL database dump -- \connect - andy SET search_path = public, pg_catalog; -- -- TOC entry 16 (OID 17508) -- Name: teams; Type: TABLE; Schema: public; Owner: andy -- CREATE TABLE teams ( teamid integer NOT NULL, name character varying(200) ); -- -- Data for TOC entry 44 (OID 17508) -- Name: teams; Type: TABLE DATA; Schema: public; Owner: andy -- COPY teams (teamid, name) FROM stdin; 101 1. FC Köln 107 1860 München 108 VfB Stuttgart 109 1. FC Kaiserslautern 103 Werder Bremen 114 Herta BSC Berlin 115 Hamburger SV 16 FC Bayern München 118 1. FC Nürnberg 122 Bayer 04 Leverkusen 120 Borussia M'gladbach 117 SC Freiburger 116 Borussia Dortmund 121 Hannover 96 112 1. FSV Mainz 05 113 Hansa Rostock 110 Schalke 04 145 VfL Wolfsburg 146 VfL Bochum 147 DSC Arminia Bielefeld \. -- -- TOC entry 29 (OID 17621) -- Name: teams_pkey; Type: CONSTRAINT; Schema: public; Owner: andy -- ALTER TABLE ONLY teams ADD CONSTRAINT teams_pkey PRIMARY KEY (teamid);