Here's a review comment. Just one for now.
Looking at the meta module, I see things like this:
execute 'select (count(*) = 1) from ' ||
quote_ident((row_id::meta.schema_id).name) || '.' ||
quote_ident((row_id::meta.relation_id).name) ||
' where ' ||
On Fri, Sep 8, 2017 at 6:57 AM Tom Lane wrote:
> Ron Johnson writes:
> > Based on LENGTH(offending_column), none of the values are more than 144
> > bytes in this 44.2M row table. Even though VARCHAR is, by definition,
> > variable length, are there
On 8 September 2017 at 15:34, chiru r wrote:
> We have multiple SAP applications running on Oracle as backend and looking
> for an opportunity to migrate from Oracle to PostgreSQL. Has anyone ever
> deployed SAP on PostgreSQL community edition?
>
> Is PostgreSQL community
On 9/8/2017 12:34 PM, chiru r wrote:
We have multiple SAP applications running on Oracle as backend and
looking for an opportunity to migrate from Oracle to PostgreSQL. Has
anyone ever deployed SAP on PostgreSQL community edition?
Is PostgreSQL community involved in any future road-map of
Hi All,
We have multiple SAP applications running on Oracle as backend and looking
for an opportunity to migrate from Oracle to PostgreSQL. Has anyone ever
deployed SAP on PostgreSQL community edition?
Is PostgreSQL community involved in any future road-map of SAP application
deployment on
On Thu, Sep 7, 2017 at 10:48 PM, Ron Johnson wrote:
> Hi,
>
> v 9.2.7
>
> Based on LENGTH(offending_column), none of the values are more than 144
> bytes in this 44.2M row table. Even though VARCHAR is, by definition,
> variable length, are there any internal design issues
Ron Johnson writes:
> Based on LENGTH(offending_column), none of the values are more than 144
> bytes in this 44.2M row table. Even though VARCHAR is, by definition,
> variable length, are there any internal design issues which would make
> things more efficient if it
>> On Thu, Sep 7, 2017 at 3:28 PM wrote:
>>
>> > Example query
>> > select a.col1, case when a.col2 > 0 then a.col3 else b.xcol1 end as mycol3
>> > from a left join b on
>> > Expected response
>> > col1 mycol3
>> >
>>
>> This may be overkill, but works:
>>
>>