[GENERAL] hstore - jsonb

Hi, A few questions about jsonb and hstore: 1. does jsonb replace hstore? 2. compatibility of jsonb hstore? 3. will the development of hstore continue? 4. is it recommended to use jsonb when planning new projects? Thanks Armand -- Sent via pgsql-general mailing list

Re: [GENERAL] COPY from CSV, passing in default value?

A more elegant way is to include the create table and copy into a function and pass the default values to this function. Am 17/05/2012 03:35, schrieb adebarros: Hi, Ben, Thanks for the suggestion. I do realize I could create the default value for the column; however, I probably should have

[GENERAL] Psql dosent log error messages on windows

When i execute a sql script trough psql, it shows me errors in the console window but it dosent write this errors in a log file. psql.exe -h localhost -d test -U postgres -w -f C:/test_files/test.sql C:/test_files/pg.log psql.exe -h localhost -d test -U postgres -w -f C:/test_files/test.sql

[GENERAL] json data type

Hi, A project in which i'm involved, make use of json data type for storing some data sets. I have read that there is some work in progress to implement json datatype support in postgres. So my question is; when and in which version of postgres we can expect this implementation? Thanks,

Re: [GENERAL] json data type

On 23/11/2010 09:34, Mike Christensen wrote: I'd be interested in knowing what functionality would come with a JSON data type, like could you query for all rows with an X property of 5 or something, eg {Y: 1, X: 6} Yes, as far as i know, you can make queries on json content

[GENERAL] rule which unpredictable modify a sequence number

I have a problem with a rule which unpredictable modify a sequence number. When I add a new table entry, the new id_keyword hasnt the value as expected. ex.: 1000, 1001, 1002,.. If i remove the rule it works. Here the table, rule and sequence definitions:

[GENERAL] rule which unpredictable modify a sequence number

I have a problem with a rule which unpredictable modify a sequence number. When I add a new table entry, the new id_keyword hasnt the value as expected. ex.: 1000, 1001, 1002,.. If i remove the rule it works. Here the table, rule and sequence

[GENERAL] varchar[] or text[]

Hi, I know this issue was controversed discussed. Some one see no really benefits of using varchar against text var. But i'm asking me what if i use it as array values. Is there any difference between varchar[126], varchar[1] and text[] else than the number of chars i can store in?

[GENERAL] index or not

Hi, Does it make sense to create indexes on a table which only contains bigint fields? Is there any performance gain? Example: Table x_rel id_a bigint id_b bigint id_c bigint id_d bigint Thanks for replying, Armand

[GENERAL] one null value in array isnt allowed???

Hi, Updating an array field with one null value isnt possible: UPDATE table SET integer_array = ARRAY[NULL] But those queries are working: UPDATE table SET integer_array = ARRAY[NULL,1] UPDATE table SET integer_array = ARRAY[1,NULL] This dosent seems logical to me. Is it a bug? Thanks for