#57 closed task (wontfix)
Backslash escaping in PostgreSQL avoids import in MySQL
| Reported by: | christoph | Owned by: | astrid |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | database | Version: | 2.4.2 rc1 |
| Keywords: | Cc: | astrid_emde |
Description
When a string contains a backslash, PostgreSQL escapes the string by "E":
example
E'<select id=
style
name=
style
>
<option value=
0
>...</option>
<option value=
1
>thin</option>
<option value=
2
>medium</option>
<option value=
3
>thick</option>
</select>', 1, 1);
The issue is discussed here:
http://archives.postgresql.org/pgsql-hackers/2005-05/msg01525.php
Maybe we need to make sure to insert only double quotes (") and no escaped single quotes (\')
Change History (6)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Version: | 2.4.2 → 2.4.2 rc1 |
|---|
comment:3 by , 17 years ago
| Type: | defect → task |
|---|
comment:4 by , 16 years ago
| Cc: | added |
|---|---|
| Milestone: | → 3.0 release |
comment:5 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
mysql-support is dropped, so no need for this functionality
Note:
See TracTickets
for help on using tickets.
Mapbender Wiki
http://www.mapbender.org/index.php/How_to_create_the_SQL_dump_for_the_release#MySQL