Обсуждение: BUG #14338: Problems of quotes with very long text

Поиск
Список
Период
Сортировка

BUG #14338: Problems of quotes with very long text

От
belhaouane.eddy@gmail.com
Дата:
VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz
aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDMzOApMb2dnZWQgYnk6ICAg
ICAgICAgIGVkZHlkZXYwMwpFbWFpbCBhZGRyZXNzOiAgICAgIGJlbGhhb3Vh
bmUuZWRkeUBnbWFpbC5jb20KUG9zdGdyZVNRTCB2ZXJzaW9uOiA5LjUuNApP
cGVyYXRpbmcgc3lzdGVtOiAgIFdpbmRvd3MgNwpEZXNjcmlwdGlvbjogICAg
ICAgIAoKSSBmb3VuZCBzb21ldGhpbmcgd2VpcmQgd2hlbiBJIHNpbXBseSB0
cnkgdG8gc2luZ2xlIHF1b3RlIGEgdmVyeSBsb25nIHRleHQKbGlrZSBhIHRl
eHQgd2l0aCA1MjYzNjYgY2hhcmFjdGVycy4NCg0KRXhhbXBsZTogSW4gdGhl
IFNRTCBleGVjdXRpb24gaW50ZXJmYWNlLCBJIGNvcGllZCBhIHRleHQgd2l0
aCA1MjYzNjYKY2hhcmFjdGVycyBhbmQgdGhlbiB3aGVuIEkgZG8gJycgYW5k
IHBhc3RlIG15X3RleHQgaW5zaWRlIHRoZSBxdW90ZS4gdGhlCmludGVyZmFj
ZSBjaGFuZ2UgdGhlIHRleHQgbGlrZSByYW5kb21seS4gVGhlcmUgaXMgYW55
IHNvbHV0aW9uIHRvIGVudGVyIGEKdmVyeSBsb25nIHRleHQgaW5zaWRlIHF1
b3Rlcz8NCg0KVGhhbmtzIGZvciBoZWxwaW5nIGd1eXMhISEhIQ0KICAKCg==

Re: BUG #14338: Problems of quotes with very long text

От
Pavel Stehule
Дата:
Hi

2016-09-25 15:50 GMT+02:00 <belhaouane.eddy@gmail.com>:

> The following bug has been logged on the website:
>
> Bug reference:      14338
> Logged by:          eddydev03
> Email address:      belhaouane.eddy@gmail.com
> PostgreSQL version: 9.5.4
> Operating system:   Windows 7
> Description:
>
> I found something weird when I simply try to single quote a very long text
> like a text with 526366 characters.
>
> Example: In the SQL execution interface, I copied a text with 526366
> characters and then when I do '' and paste my_text inside the quote. the
> interface change the text like randomly. There is any solution to enter a
> very long text inside quotes?
>
> Thanks for helping guys!!!!!
>
>
>
500 kB is not too much for Postgres, but maybe is too for your client.

The most simple way is using Large Object interface - you can use psql
command \lo_import. Next step is converting imported large object to
string. An example is demonstration of import large JSON document.

postgres=# \lo_import ~/citylots.json
lo_import 16510
CREATE OR REPLACE FUNCTION public.bytea_to_text(bytea)
 RETURNS text
 LANGUAGE sql
AS $function$
SELECT convert_from($1, current_setting('server_encoding'))
$function$

CREATE TABLE city_text(data text);
INSERT INTO city_text SELECT bytea_to_text(lo_get(16510));
CREATE TABLE city_json(data json);
CREATE TABLE city_jsonb(data jsonb);
INSERT INTO city_json SELECT data::json FROM city_text;
INSERT INTO city_jsonb SELECT data::jsonb FROM city_text;

Probably this is not PostgreSQL bug - please, use psql-general mailing list.

Regards

Pavel




> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>