sfst

So it can be closed?

According to https://discussion.evernote.com/forums/topic/138075-weird-characters-are-added-to-printed-in-my-note-when-entering-a-shortcut/ there is a problem when the default language is Dutch. Switching to English (US) apparently helps?

Time is passing fast :-) Another year passed, so maybe it is no longer needed to be kept open? ;-)

[..]does not work on Postgres Yes, unfortunately, which is a pity, but it isn't a requirement for SQuirreL SQL to only use the intersection of capabilities of Postgres and Oracle, right? 1.) Use standard quoting and standard escaping: select 'long string with some quoted semicolon '';'' in the string.' from dual That is what I am using, but it is an inconvenience. I am often inserting SQL commands into a setup table (some modules are fetching those commands to do some daily tasks like data integrity...

I understand you kept this open, so other people can find the solution, but now after one year it can be closed?

Using squirrel-sql-snapshot-20230109_2301-standard.jar I have tried with an Oracle database to compare 2 tables in different schemata (but different sessions) and got nothing. It logged: ERROR net.sourceforge.squirrel_sql.client.Main - Exception occurred dispatching Event java.awt.event.MouseEvent[MOUSE_RELEASED,(538,836),absolute(530,868),button=1,modifiers=Button1,clickCount=1] on frame0

Version 4.5.0 still throws this error. I am not sure whether it is related to the problem that this select command: select q'{long string with some quoted semicolon ';' in the string.}' from dual; Throws: --begin quote-- Error: ORA-01756: quoted string not properly terminated SQLState: 42000 ErrorCode: 1756 Position: 79 Error occurred in: select q'{long string with some quoted semicolon ' --end quote-- FYI: This here runs fine: select q'{long string with some quoted colon ':' and double dashes '--'...

Pardon my necro-posting, but the original article on the MS site is no longer available. There is a newer version at https://docs.microsoft.com/en-US/office/troubleshoot/excel/wrongly-assumes-1900-is-leap-year (MS does NOT forward from http://support.microsoft.com/kb/214058, but they DO forward from http://support.microsoft.com/kb/214326, which apparently was a related article.) (I also noticed that in the bug report I had used "CVS", which should have been "CSV")