Hi all,
I'm trying to improve the ECPG documents for the ECPG application
developrs, because some of my clients want more detailed information
when they develop (or migrate) an embeded SQL applications.
Of course, I want to contribute this work to the official manual.
So I have one thing to intro
Heikki,
Thanks for the comments.
On 6/19/2010 0:56 Heikki Linnakangas wrote:
> A reference of all the directives seems useful, but it seems at least
> partially redundant with what's there already. WHENEVER for example is
> quite well documented at
> http://www.postgresql.org/docs/current/interac
Hi all,
I've found a bit strange thing on the INTEGER range in the official manual.
http://www.postgresql.org/docs/8.4/interactive/datatype-numeric.html
According to the official manual, the INTEGER range is "-2147483648 to
+2147483647".
However, my example in below shows that "-2147483648" is
t
on their type casting (my guess), and it's a bit tricky.
Regards,
On 2010/06/22 18:57, Thom Brown wrote:
On 22 June 2010 10:46, Thom Brown wrote:
On 22 June 2010 09:59, Satoshi Nagayasu wrote:
Magnus,
Thanks for your advice. I've understood how it happens.
However, it looks tricky an
:
On Tue, Jun 22, 2010 at 10:27 AM, Satoshi Nagayasu
wrote:
Hi all,
I've found a bit strange thing on the INTEGER range in the official manual.
http://www.postgresql.org/docs/8.4/interactive/datatype-numeric.html
According to the official manual, the INTEGER range is "-2147483648
Michael,
On 2010/06/24 21:23, Michael Meskes wrote:
Yes. One of the things what I'm afraid is that point.
How could we (re-)organize the document structure to eliminate such redundancy?
The document structure is not set in stone, if you deem it better to reorganize
it feel free to do so.
Tha
Hi all,
As I mentioned in the previous mail,
I have almost finished writing new ECPG SQLDA section.
This document is based on the current ECPG/SQLDA documents,
and added some examples to help writing SQLDA code in ECPG
for application developers.
It has following 9 sub-sections.
- Developing a
Hi all,
I have just finished to update "Using Host Variables" section,
one of the most important sections for ECPG development.
It has following 8 sub-sections.
- Host variables overview
- Mapping between PostgreSQL data types and host variable types
- Declare Sections
- Retreiving query result
Hi all,
I have just remembered I finished writing the "Large Objects" section
to describe large object handling in ECPG.
http://code.google.com/p/ecpgdocs/downloads/detail?name=Large%20objects.pdf&can=2&q=#makechanges
Please look at this document, too.
Thanks,
On 2010/07
Any feedback and comments would be appreciated.
Regards,
On 2010/06/17 18:07, Satoshi Nagayasu wrote:
> Hi all,
>
> I'm trying to improve the ECPG documents for the ECPG application
> developrs, because some of my clients want more detailed information
> when they develop (o
- Archived manual in ZIP file
http://code.google.com/p/ecpgdocs/downloads/detail?name=ecpg_html.zip
Any feedback and comments would be appreciated.
Regards,
On 2010/07/08 18:50, Satoshi Nagayasu wrote:
> Hi all,
>
> As I mentioned, I have been working to improve the ECPG offici
Hi all,
I'm looking into some ecpg part of the official manual,
and I have found some strange things.
I'm now investigating SQLCODE and SQLSTATE, and I have found
that some of the errno definitions don't match to the manual.
For example, the manual says that ECPG_CONVERT_BOOL could be `-207'.
Ho
On 2010/07/29 17:41, Michael Meskes wrote:
I had a short look at the docs Satoshi-san put online and yes, I'm impressed.
However, I won't be able to proof read them before September. But given that
9.1 development is just starting I see no problem in putting the docs into the
archive be it cvs or
On 2010/08/09 21:27, Robert Haas wrote:
I'm now investigating SQLCODE and SQLSTATE, and I have found
that some of the errno definitions don't match to the manual.
What does it mean? The manual is not up to date?
Yeah, I think that's what it means. Perhaps you could provide a patch
for the d
On 2010/08/10 1:36, Satoshi Nagayasu wrote:
On 2010/08/09 21:27, Robert Haas wrote:
I'm now investigating SQLCODE and SQLSTATE, and I have found
that some of the errno definitions don't match to the manual.
What does it mean? The manual is not up to date?
Yeah, I think that'
Hi all,
I found some typos in pgarchivecleanup.sgml.
A patch to fix them is attached in this mail.
Please take a look.
Regards,
--
NAGAYASU Satoshi
Index: pgarchivecleanup.sgml
===
--- pgarchivecleanup.sgml (revision 404)
+++
On 2010/08/12 4:08, Robert Haas wrote:
On Mon, Aug 9, 2010 at 11:29 PM, Satoshi Nagayasu
wrote:
On 2010/08/10 1:36, Satoshi Nagayasu wrote:
On 2010/08/09 21:27, Robert Haas wrote:
I'm now investigating SQLCODE and SQLSTATE, and I have found
that some of the errno definitions don&#x
Hi Peter,
Thanks for your reviewing.
On 2010/09/26 20:57, Peter Eisentraut wrote:
On tor, 2010-08-12 at 09:51 +0900, Satoshi Nagayasu wrote:
Thank you for the commit, and I'll put the remainder
to the commitfest page.
Please submit a new patch that applies on top of what was al
As a comment from Álvaro Herrera, I have made some changes around ENOMEM
from quotes to tags.
- Indicates that your virtual memory is exhausted, defined as `-ENOMEM'.
+ Indicates that your virtual memory is exhausted, defined as
-ENOMEM.
Thanks,
On 2010/09/28 7:51, Satoshi Nagayasu
On 2010/09/28 9:40, Robert Haas wrote:
Here is a new patch applicable to the cvs head.
Please check it out.
Are you aware that we have switched to git?
Oops, I visited a page describing about the coderepository
from here:
http://www.postgresql.org/developer/coding
Yeah, I know the code repo
On 2010/09/28 10:31, Greg Smith wrote:
If the patch you generated applies to the git version of the repo cleanly, you
may be fine for now. The anon-cvs version is mainly intended as a source to get
a copy of the source code just to compile or read, not to develop patches
against. For that it w
On 2010/09/28 12:40, Alvaro Herrera wrote:
Excerpts from Satoshi Nagayasu's message of lun sep 27 22:38:44 -0400 2010:
On 2010/09/28 10:31, Greg Smith wrote:
If the patch you generated applies to the git version of the repo cleanly, you
may be fine for now. The anon-cvs version is mainly inten
On 2010/09/28 14:08, Alvaro Herrera wrote:
Excerpts from Satoshi Nagayasu's message of mar sep 28 00:06:19 -0400 2010:
On 2010/09/28 12:40, Alvaro Herrera wrote:
Looking at this patch I cannot but wonder if this should be a table
instead of a plain list.
What's happen if you run the patch c
On 2010/09/26 23:32, Peter Eisentraut wrote:
On fre, 2010-07-30 at 01:23 +0900, Satoshi Nagayasu wrote:
I'm thinking about taking a few weeks after August or September
to review and merge the document intensively (like CommitFest)
by some developers who are interested in this doc.
I know
On 2010/09/29 20:04, Peter Eisentraut wrote:
On tis, 2010-09-28 at 11:38 +0900, Satoshi Nagayasu wrote:
On 2010/09/28 10:31, Greg Smith wrote:
If the patch you generated applies to the git version of the repo cleanly, you
may be fine for now. The anon-cvs version is mainly intended as a
On 2010/09/30 17:08, Magnus Hagander wrote:
Peters rsync changes only affects the developer docs. The ones you are
looking at are the 9.0.0 docs. They are "stuck" at 9.0.0 until we
release 9.0.1, which is when they'll pick up the new text about the
git repo.
If we hadn't scheduled a 9.0.1 releas
On 2010/10/10 19:55, Peter Eisentraut wrote:
On tis, 2010-09-28 at 19:01 +0900, Satoshi Nagayasu wrote:
Patch is available at here:
http://code.google.com/p/ecpgdocs/downloads/detail?name=ecpg-patches.20100928.tgz
(I uploaded this to the GoogleCode, because this list did not deliver
my
Hi all,
I just found "PL" is explained as "Programming Languages"
in the Acronyms section.
http://www.postgresql.org/docs/current/static/acronyms.html
I think this should be "Procedural Languages" because
"Procedural" is used in the Server Programming section.
http://www.postgresql.org/docs/cur
Hi,
2011/06/03 18:16, Marc Cousin wrote:
Hi, we're translating the ecpg.xml from scratch in french, as it seems
to have moved a lot with 9.0 and 9.1.
I'm having trouble with this:
3948desc_next
3949
3950
3951 If the query returns more than one records, multiple linked
SQLDA structures
uffer management algorithm.
I think it should be described as "Clock-sweep count" or something
like that.
And I'd like to add some additional explanation for the "forknumber"
as below:
"0 for heap file, 1 for FreeSpaceMap, and 2 for VisibilityMap".
Any comment
Thanks, Bruce!
2013/07/04 3:26, Bruce Momjian wrote:
On Wed, Jul 3, 2013 at 02:23:11PM -0400, Bruce Momjian wrote:
On Sat, Nov 24, 2012 at 11:57:51AM +0900, Satoshi Nagayasu wrote:
Hi,
I found that the manual page for pg_buffercache module explains
"usagecount" as "Page LR
view my English.
Regards,
--
Satoshi Nagayasu
Uptime Technologies, LLC. http://www.uptime.jp
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
X online with believing in the explanation.
So, I think we should improve this explanation precisely not to lead
such misunderstanding.
What do you think? Any comments?
Regards,
--
Satoshi Nagayasu
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subs
2016-09-09 22:41 GMT+09:00 Tom Lane :
> Satoshi Nagayasu writes:
>> According to the manual, running REINDEX does not take any locks
>> on the parent table which block read operations.
>> Actually, REINDEX blocks SELECT queries, maybe in the planning phase.
>
> Hm.
34 matches
Mail list logo
