On Aug 27, 2012 12:58 AM, "Wolfgang Keller" wrote:
>
> > 1) First, in LedgerSMB,
>
>
>
> What a pity that this is implemented in a write-only programming
> language and as a "web application" instead of an actual GUI...
>
>
Actually this has continued to remind me how ugly HTTP is for actual
a
> 1) First, in LedgerSMB,
What a pity that this is implemented in a write-only programming
language and as a "web application" instead of an actual GUI...
> we started using it to create consistent interfaces to sets of
> storage tables. The storage tables would behave differently, but
> w
Hi,
On 24 August 2012 11:44, Chris Travers wrote:
> One thing I have found looking through Oracle and DB2 docs is that
> their table inheritance seems to have all the same problems as ours
> and their solutions to these problems seem rather broken from a
> pure relational perspective.
I can
One other thing that seems worth mentioning is that as soon as you
jump from relational to object-relational modelling is that the latter
is more rich and hence more complex than the former. Because
object-relational modelling is a much expanded semantic superset of
relational modelling, the antip
On Thu, Aug 23, 2012 at 12:36 PM, Merlin Moncure wrote:
> On Wed, Aug 22, 2012 at 10:22 PM, Chris Travers
> wrote:
>> I have now been working with table inheritance for a while and after
>> starting to grapple with many of the use cases it has have become
>> increasingly impressed with this feat
On Wed, Aug 22, 2012 at 10:22 PM, Chris Travers wrote:
> I have now been working with table inheritance for a while and after
> starting to grapple with many of the use cases it has have become
> increasingly impressed with this feature. I also think that some of
> the apparent limitations fundam
On Aug 22, 2012, at 23:22, Chris Travers wrote:
> * unique constraints being able to be marked INHERIT or NOINHERIT.
> A unique constraint that is marked INHERIT would be automatically
> created again on the child table. This could be documented to be
> domain-specific to each child table, and
I have now been working with table inheritance for a while and after
starting to grapple with many of the use cases it has have become
increasingly impressed with this feature. I also think that some of
the apparent limitations fundamentally follow from the support for
multiple inheritance, and mu
