We are using postgres9 and aggregate 1.4.7. We find ourselves having to
re-create DB permissions for the new tables every time a new version is
uploaded and new tables are created by uploading a form definition. If we
create a table manually it inherits the default permissions fine, but not
for those created by form definition upload.
Does anyone have experience with / an explanation / a fix for this issue?
Did you run the create_db_and_user.sql script when setting up the
PostgreSQL database?
That should have granted full creation rights to the database account set
up for ODK Aggregate.
Or has PostgreSQL changed the inheritance and delegation of those rights in
the last 5 years?
We tested it way back on PostgreSQL 9.1
I don't think anything this substantial would have changed in a minor
release.
···
On Wed, Sep 21, 2016 at 8:30 AM, Jason Ives wrote:
We are using postgres9 and aggregate 1.4.7. We find ourselves having to
re-create DB permissions for the new tables every time a new version is
uploaded and new tables are created by uploading a form definition. If we
create a table manually it inherits the default permissions fine, but not
for those created by form definition upload.
Does anyone have experience with / an explanation / a fix for this issue?
Yes, we are running create_db_and_user.sql script. Currently we are
running postgresql 9.2.15-1.el7_2.
The issue we are seeing is that when ODK creates a new table, the new
tables don’t inherit the default privileges. We have assigned the
privileges at both the database and schema level.
Anyone else seen this issue?
Jason
···
On Wednesday, September 21, 2016 at 2:26:57 PM UTC-4, Mitch Sundt wrote:
>
> Did you run the create_db_and_user.sql script when setting up the
> PostgreSQL database?
>
> That should have granted full creation rights to the database account set
> up for ODK Aggregate.
>
> Or has PostgreSQL changed the inheritance and delegation of those rights
> in the last 5 years?
>
> We tested it way back on PostgreSQL 9.1
>
> I don't think anything this substantial would have changed in a minor
> release.
>
>
> On Wed, Sep 21, 2016 at 8:30 AM, Jason Ives <jas...@gmail.com > wrote:
>
>> We are using postgres9 and aggregate 1.4.7. We find ourselves having to
>> re-create DB permissions for the new tables every time a new version is
>> uploaded and new tables are created by uploading a form definition. If we
>> create a table manually it inherits the default permissions fine, but not
>> for those created by form definition upload.
>>
>> Does anyone have experience with / an explanation / a fix for this issue?
>>
>> Let me know if more info is needed.
>>
>> Thanks
>> Jason
>>
>> --
>> --
>> Post: opend...@googlegroups.com
>> Unsubscribe: opendatakit...@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ODK Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opendatakit...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
>
Has this ever worked the way you expected? What, if anything changed,
before you noticed the problem?
Yaw
···
On Mon, Sep 26, 2016 at 7:12 PM, Jason Ives wrote:
> Thanks Mitch,
>
> Yes, we are running create_db_and_user.sql script. Currently we are running
> postgresql 9.2.15-1.el7_2.
>
> The issue we are seeing is that when ODK creates a new table, the new tables
> don’t inherit the default privileges. We have assigned the privileges at
> both the database and schema level.
>
> Anyone else seen this issue?
>
> Jason
>
> On Wednesday, September 21, 2016 at 2:26:57 PM UTC-4, Mitch Sundt wrote:
>>
>> Did you run the create_db_and_user.sql script when setting up the
>> PostgreSQL database?
>>
>> That should have granted full creation rights to the database account set
>> up for ODK Aggregate.
>>
>> Or has PostgreSQL changed the inheritance and delegation of those rights
>> in the last 5 years?
>>
>> We tested it way back on PostgreSQL 9.1
>>
>> I don't think anything this substantial would have changed in a minor
>> release.
>>
>>
>> On Wed, Sep 21, 2016 at 8:30 AM, Jason Ives wrote:
>>>
>>> We are using postgres9 and aggregate 1.4.7. We find ourselves having to
>>> re-create DB permissions for the new tables every time a new version is
>>> uploaded and new tables are created by uploading a form definition. If we
>>> create a table manually it inherits the default permissions fine, but not
>>> for those created by form definition upload.
>>>
>>> Does anyone have experience with / an explanation / a fix for this issue?
>>>
>>> Let me know if more info is needed.
>>>
>>> Thanks
>>> Jason
>>>
>>> --
>>> --
>>> Post: opend...@googlegroups.com
>>> Unsubscribe: opendatakit...@googlegroups.com
>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google Groups
>>> "ODK Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to opendatakit...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>> --
>> Mitch Sundt
>> Software Engineer
>> University of Washington
>> mitche...@gmail.com
>
> --
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "ODK Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to opendatakit+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Thanks for checking in on this. No, it has never functioned as expected,
always as described below.
Jason
···
On Tuesday, September 27, 2016 at 5:31:28 AM UTC-4, Yaw Anokwa wrote:
>
> Hi Jason,
>
> Has this ever worked the way you expected? What, if anything changed,
> before you noticed the problem?
>
> Yaw
>
> On Mon, Sep 26, 2016 at 7:12 PM, Jason Ives <jas...@gmail.com > wrote:
> > Thanks Mitch,
> >
> > Yes, we are running create_db_and_user.sql script. Currently we are
> running
> > postgresql 9.2.15-1.el7_2.
> >
> > The issue we are seeing is that when ODK creates a new table, the new
> tables
> > don’t inherit the default privileges. We have assigned the privileges
> at
> > both the database and schema level.
> >
> > Anyone else seen this issue?
> >
> > Jason
> >
> > On Wednesday, September 21, 2016 at 2:26:57 PM UTC-4, Mitch Sundt wrote:
> >>
> >> Did you run the create_db_and_user.sql script when setting up the
> >> PostgreSQL database?
> >>
> >> That should have granted full creation rights to the database account
> set
> >> up for ODK Aggregate.
> >>
> >> Or has PostgreSQL changed the inheritance and delegation of those
> rights
> >> in the last 5 years?
> >>
> >> We tested it way back on PostgreSQL 9.1
> >>
> >> I don't think anything this substantial would have changed in a minor
> >> release.
> >>
> >>
> >> On Wed, Sep 21, 2016 at 8:30 AM, Jason Ives wrote:
> >>>
> >>> We are using postgres9 and aggregate 1.4.7. We find ourselves having
> to
> >>> re-create DB permissions for the new tables every time a new version
> is
> >>> uploaded and new tables are created by uploading a form definition.
> If we
> >>> create a table manually it inherits the default permissions fine, but
> not
> >>> for those created by form definition upload.
> >>>
> >>> Does anyone have experience with / an explanation / a fix for this
> issue?
> >>>
> >>> Let me know if more info is needed.
> >>>
> >>> Thanks
> >>> Jason
> >>>
> >>> --
> >>> --
> >>> Post: opend...@googlegroups.com
> >>> Unsubscribe: opendatakit...@googlegroups.com
> >>> Options: http://groups.google.com/group/opendatakit?hl=en
> >>>
> >>> ---
> >>> You received this message because you are subscribed to the Google
> Groups
> >>> "ODK Community" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> an
> >>> email to opendatakit...@googlegroups.com.
> >>> For more options, visit https://groups.google.com/d/optout.
> >>
> >>
> >>
> >>
> >> --
> >> Mitch Sundt
> >> Software Engineer
> >> University of Washington
> >> mitche...@gmail.com
> >
> > --
> > --
> > Post: opend...@googlegroups.com
> > Unsubscribe: opendatakit...@googlegroups.com
> > Options: http://groups.google.com/group/opendatakit?hl=en
> >
> > ---
> > You received this message because you are subscribed to the Google
> Groups
> > "ODK Community" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to opendatakit...@googlegroups.com .
> > For more options, visit https://groups.google.com/d/optout.
>
Interesting. I've filed the issue at https://github.com/opendatakit/opendatakit/issues/1255. What would
help is if you could try installing on a clean VM with Aggregate
1.4.12, Tomcat 6, and PostgreSQL 9.1 and see if you can reproduce it.
If you can, then describe the steps in that issue so the core team can
repro it. Basically, we need to understand if this is an issue with
your infrastructure or with the version of Postgres or with the
version of Aggregate.
Anyone else with PostgreSQL having this problem?
Yaw
···
On Thu, Sep 29, 2016 at 9:35 PM, Jason Ives wrote:
> Hi Yaw,
>
> Thanks for checking in on this. No, it has never functioned as expected,
> always as described below.
>
> Jason
>
> On Tuesday, September 27, 2016 at 5:31:28 AM UTC-4, Yaw Anokwa wrote:
>>
>> Hi Jason,
>>
>> Has this ever worked the way you expected? What, if anything changed,
>> before you noticed the problem?
>>
>> Yaw
>>
>> On Mon, Sep 26, 2016 at 7:12 PM, Jason Ives wrote:
>> > Thanks Mitch,
>> >
>> > Yes, we are running create_db_and_user.sql script. Currently we are
>> > running
>> > postgresql 9.2.15-1.el7_2.
>> >
>> > The issue we are seeing is that when ODK creates a new table, the new
>> > tables
>> > don’t inherit the default privileges. We have assigned the privileges
>> > at
>> > both the database and schema level.
>> >
>> > Anyone else seen this issue?
>> >
>> > Jason
>> >
>> > On Wednesday, September 21, 2016 at 2:26:57 PM UTC-4, Mitch Sundt wrote:
>> >>
>> >> Did you run the create_db_and_user.sql script when setting up the
>> >> PostgreSQL database?
>> >>
>> >> That should have granted full creation rights to the database account
>> >> set
>> >> up for ODK Aggregate.
>> >>
>> >> Or has PostgreSQL changed the inheritance and delegation of those
>> >> rights
>> >> in the last 5 years?
>> >>
>> >> We tested it way back on PostgreSQL 9.1
>> >>
>> >> I don't think anything this substantial would have changed in a minor
>> >> release.
>> >>
>> >>
>> >> On Wed, Sep 21, 2016 at 8:30 AM, Jason Ives wrote:
>> >>>
>> >>> We are using postgres9 and aggregate 1.4.7. We find ourselves having
>> >>> to
>> >>> re-create DB permissions for the new tables every time a new version
>> >>> is
>> >>> uploaded and new tables are created by uploading a form definition.
>> >>> If we
>> >>> create a table manually it inherits the default permissions fine, but
>> >>> not
>> >>> for those created by form definition upload.
>> >>>
>> >>> Does anyone have experience with / an explanation / a fix for this
>> >>> issue?
>> >>>
>> >>> Let me know if more info is needed.
>> >>>
>> >>> Thanks
>> >>> Jason
>> >>>
>> >>> --
>> >>> --
>> >>> Post: opend...@googlegroups.com
>> >>> Unsubscribe: opendatakit...@googlegroups.com
>> >>> Options: http://groups.google.com/group/opendatakit?hl=en
>> >>>
>> >>> ---
>> >>> You received this message because you are subscribed to the Google
>> >>> Groups
>> >>> "ODK Community" group.
>> >>> To unsubscribe from this group and stop receiving emails from it, send
>> >>> an
>> >>> email to opendatakit...@googlegroups.com.
>> >>> For more options, visit https://groups.google.com/d/optout.
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Mitch Sundt
>> >> Software Engineer
>> >> University of Washington
>> >> mitche...@gmail.com
>> >
>> > --
>> > --
>> > Post: opend...@googlegroups.com
>> > Unsubscribe: opendatakit...@googlegroups.com
>> > Options: http://groups.google.com/group/opendatakit?hl=en
>> >
>> > ---
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "ODK Community" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an
>> > email to opendatakit...@googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "ODK Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to opendatakit+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
The ODK Aggregate database username must be granted read access to the
information_schema.columns
table. If you have restricted that user to only have access to the schema
used by ODK Aggregate, then this might be why you are having trouble. In
general, this user should be granted read access to anything in the
information_schema
···
On Fri, Sep 30, 2016 at 1:36 AM, Yaw Anokwa wrote:
Hi Jason,
Interesting. I've filed the issue at https://github.com/opendatakit/opendatakit/issues/1255. What would
help is if you could try installing on a clean VM with Aggregate
1.4.12, Tomcat 6, and PostgreSQL 9.1 and see if you can reproduce it.
If you can, then describe the steps in that issue so the core team can
repro it. Basically, we need to understand if this is an issue with
your infrastructure or with the version of Postgres or with the
version of Aggregate.
Anyone else with PostgreSQL having this problem?
Yaw
On Thu, Sep 29, 2016 at 9:35 PM, Jason Ives jasives@gmail.com wrote:
Hi Yaw,
Thanks for checking in on this. No, it has never functioned as expected,
always as described below.
Jason
On Tuesday, September 27, 2016 at 5:31:28 AM UTC-4, Yaw Anokwa wrote:
Hi Jason,
Has this ever worked the way you expected? What, if anything changed,
before you noticed the problem?
Yaw
On Mon, Sep 26, 2016 at 7:12 PM, Jason Ives jas...@gmail.com wrote:
Thanks Mitch,
Yes, we are running create_db_and_user.sql script. Currently we are
running
postgresql 9.2.15-1.el7_2.
The issue we are seeing is that when ODK creates a new table, the new
tables
don’t inherit the default privileges. We have assigned the privileges
at
both the database and schema level.
Anyone else seen this issue?
Jason
On Wednesday, September 21, 2016 at 2:26:57 PM UTC-4, Mitch Sundt wrote:
Did you run the create_db_and_user.sql script when setting up the
PostgreSQL database?
That should have granted full creation rights to the database account
set
up for ODK Aggregate.
Or has PostgreSQL changed the inheritance and delegation of those
rights
in the last 5 years?
We tested it way back on PostgreSQL 9.1
I don't think anything this substantial would have changed in a minor
release.
On Wed, Sep 21, 2016 at 8:30 AM, Jason Ives jas...@gmail.com wrote:
We are using postgres9 and aggregate 1.4.7. We find ourselves
having
to
re-create DB permissions for the new tables every time a new version
is
uploaded and new tables are created by uploading a form definition.
If we
create a table manually it inherits the default permissions fine,
but
not
for those created by form definition upload.
Does anyone have experience with / an explanation / a fix for this
issue?
You received this message because you are subscribed to the Google
Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it,
send
an
email to opendatakit...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington mitche...@gmail.com
You received this message because you are subscribed to the Google
Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to opendatakit...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.