On Fri, 2009-07-03 at 13:38 -0400, Robert Treat wrote:
> On Thursday 02 July 2009 12:40:49 Simon Riggs wrote:
> > On Wed, 2009-07-01 at 11:19 -0400, Caleb Cushing wrote:
> > > A couple of times I've been told "you don't need tinyint, use boolean"
> > > which is not true, several projects I've work
On Jul 3, 2009, at 11:56 PM, Tom Lane wrote:
Robert Haas writes:
On Fri, Jul 3, 2009 at 4:00 PM, Tom Lane wrote:
"Kevin Grittner" writes:
It seems to be inconsistent. Probably because everything wound up
with the same date, the order is probably more-or-less random.
Yeah, I think that's
On Fri, Jul 3, 2009 at 8:19 PM, Tom Lane wrote:
> The main reason contrib still has the alternate method is that PGXS
> doesn't really work until after you've installed the core build.
> For modules distributed separately from core, it doesn't seem that
> exciting to be able to build using the cont
Hi,
in a continued effort for better Informix ESQL/C compatibility,
we added the "string" pseudo-type handling to ECPG.
This type in ESQL/C is documented as:
--
The string Data Type
The string data type is an ESQL/C data type that holds character d
Boszormenyi Zoltan writes:
> in a continued effort for better Informix ESQL/C compatibility,
> we added the "string" pseudo-type handling to ECPG.
> ...
> - "string" has become a type name, reserved word in ECPG.
This seems like a sufficient reason to reject the patch. Who knows
what that will b
Hi,
Tom Lane írta:
> Boszormenyi Zoltan writes:
>
>> in a continued effort for better Informix ESQL/C compatibility,
>> we added the "string" pseudo-type handling to ECPG.
>> ...
>> - "string" has become a type name, reserved word in ECPG.
>>
>
> This seems like a sufficient reason to rej
Hello,
I can't to find reason of my problem. I have a varlena type. This type
works well with plain storage, but this raise some random exception
with extended storage. It finish on Assert((data - start) ==
data_size)[heaptuple.c]; I checked - when I return varlena from in
function, then it has co
It's pretty hard to guess where your bug is sitting here with no code
and no idea even what you've done to trigger it.
At a guess there someplace you haven't detoasted a datum that had to
be detoasted. But like I said that's just a guess.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@pos
On Sat, Jul 4, 2009 at 10:31 PM, Greg Stark wrote:
> It's pretty hard to guess where your bug is sitting here with no code
> and no idea even what you've done to trigger it.
>
> At a guess there someplace you haven't detoasted a datum that had to
> be detoasted. But like I said that's just a guess.
On Saturday 04 July 2009 01:19:23 Joshua D. Drake wrote:
> On Fri, 2009-07-03 at 17:57 -0400, Robert Haas wrote:
> > I guess I'm not really seeing why that particular thing should be a
> > button rather than a link. It would mess up the formatting for no
> > obvious benefit.
>
> Not arguing one wa
Le 5 juil. 09 à 00:13, Peter Eisentraut a écrit :
On Saturday 04 July 2009 01:19:23 Joshua D. Drake wrote:
Not arguing one way or the other, a button says, "I am about to
perform
X". A link *always* says, "I am about to go to a new web page".
That was my feeling.
And bots (google etc) will
On Jul 4, 2009, at 5:18 PM, Dimitri Fontaine
wrote:
Le 5 juil. 09 à 00:13, Peter Eisentraut a écrit :
On Saturday 04 July 2009 01:19:23 Joshua D. Drake wrote:
Not arguing one way or the other, a button says, "I am about to
perform
X". A link *always* says, "I am about to go to a new web p
Joe Conway wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> >> Alvaro Herrera writes:
> >>> Consistency here is pointless. IIRC the dual method is used in contrib
> >>> because people did not trust the PGXS stuff enough to rip the original
> >>> Make code out; or maybe because people did not w
2009/7/4 Greg Stark :
> On Sat, Jul 4, 2009 at 10:31 PM, Greg Stark wrote:
>> It's pretty hard to guess where your bug is sitting here with no code
>> and no idea even what you've done to trigger it.
>>
see attachment - sorry, comments are czech
>> At a guess there someplace you haven't detoasted
2009/7/3 Robert Haas :
> The application stamps comments with the
> community login of the person who left them, but the import stamped
> them with names instead. This is actually of some significance, since
> the app will allow you to edit your own comments but not those of
> other people. We co
15 matches
Mail list logo
