, Yourfriend doudou...@gmail.com wrote:
for example, SO201507_1001, PO201503_1280, etc.
As these IDs would be the most important attribute to the business, so,
we
hope there is no gap for the IDs.
That's a requirement I've heard a number of times before. If you're
relying on a sequence
.
As these IDs would be the most important attribute to the business, so, we
hope there is no gap for the IDs.
Regards,
Daojing Zhou.
On Wed, Jul 15, 2015 at 2:33 AM, Peter Geoghegan p...@heroku.com wrote:
On Sun, Jul 12, 2015 at 4:09 AM, Yourfriend doudou...@gmail.com wrote:
Suggestion: When
Hi, Hackers,
The feature of UPSERT was my most interested one of 9.5, I really like
need it.
I have test the different usages for this features like one record input,
multi records input,
and also more than 10,000 records upserting, all look great, thanks for
your work.
When I checked my
Dear all,
In our company, we use both PostgreSQL and MySQL, our developers include me
think that the INSERT ... ON DUPLICATE UPDATE clause is a much more user
friendly function,so, would you please add this liked function in
PostgreSQL, I know we can write PROCEDURE or RULE to solve this
According to the release notes of 8.2, the following item should have been implemented, E.1.3.11.
psql ChangesSave multi-line statements as a single entry, rather than
one line at a time (Sergey E. Koposov)
This makes up-arrow recall of queries easier.
The
