You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <de...@bloodhound.apache.org> on 2013/07/22 03:31:22 UTC
[Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
-----------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: dashboard | Version:
Keywords: |
-----------------------+--------------------
==== How to Reproduce ====
While doing a POST operation on `/newticket`, Trac issued an internal
error.
''(please provide additional details here)''
Request parameters:
{{{
{'__FORM_TOKEN': u'c0b60abc8107497945866914',
'comment': u'',
'field_cc': u'',
'field_description': u'',
'field_keywords': u'',
'field_reporter': u'lok',
'field_severity': u'none',
'field_summary': u'aaaaaaaa',
'start_time': u'0',
'submit': u'Create ticket',
'view_time': u'0'}
}}}
User agent: `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36`
==== System Information ====
|| '''`Trac`''' || `1.0.1` [[br]] `` ||
|| '''`Babel`''' || `0.9.6` ||
|| '''`Bloodhound Trac`''' || `1.0.1` ||
|| '''`Genshi`''' || `0.7 (without speedups)` ||
|| '''`mod_wsgi`''' || `3.3 (WSGIProcessGroup bloodhound_tracker
WSGIApplicationGroup %{GLOBAL})` ||
|| '''`psycopg2`''' || `2.4.5` ||
|| '''`Pygments`''' || `1.6` ||
|| '''`Python`''' || `2.7.3 (default, Apr 10 2013, 06:31:07) ` [[br]]
`[GCC 4.6.3]` ||
|| '''`pytz`''' || `2013b` ||
|| '''`setuptools`''' || `0.6` ||
|| '''`jQuery`''' || `1.7.2` ||
==== Enabled Plugins ====
|| '''`bhrelations.widgets.relations`''' || `N/A` ||
|| '''`BloodhoundDashboardPlugin`''' || `0.6.0` ||
|| '''`BloodhoundMultiProduct`''' || `0.6.0` ||
|| '''`BloodhoundRelationsPlugin`''' || `0.6.0` ||
|| '''`BloodhoundSearchPlugin`''' || `0.6.0` ||
|| '''`BloodhoundTheme`''' || `0.6.0` ||
|| '''`TracAccountManager`''' || `0.4.3` ||
|| '''`TracPermRedirect`''' || `3.0` ||
|| '''`TracThemeEngine`''' || `2.2.0` ||
==== Python Traceback ====
{{{
Traceback (most recent call last):
File "/opt/apache-bloodhound-0.6/trac/trac/web/main.py", line 477, in
_dispatch_request
dispatcher.dispatch(req)
File "/opt/apache-bloodhound-0.6/trac/trac/web/main.py", line 214, in
dispatch
resp = chosen_handler.process_request(req)
File "/opt/apache-bloodhound-0.6/trac/trac/ticket/web_ui.py", line 180,
in process_request
return self._process_newticket_request(req)
File "/opt/apache-bloodhound-0.6/trac/trac/ticket/web_ui.py", line 465,
in _process_newticket_request
self._do_create(req, ticket) # (redirected if successful)
File "/opt/apache-bloodhound-0.6/trac/trac/ticket/web_ui.py", line 1289,
in _do_create
ticket.insert()
File "/opt/apache-bloodhound-0.6/trac/trac/ticket/model.py", line 241,
in insert
[values[name] for name in std_fields])
File "/opt/apache-
bloodhound-0.6/bloodhound_multiproduct/multiproduct/dbcursor.py", line
143, in execute
return self.cursor.execute(sql, args=args)
File "/opt/apache-
bloodhound-0.6/bloodhound_multiproduct/multiproduct/dbcursor.py", line 83,
in execute
return super(BloodhoundIterableCursor,
self).execute(translate_sql(self.env, sql), args=args)
File "/opt/apache-bloodhound-0.6/trac/trac/db/util.py", line 65, in
execute
return self.cursor.execute(sql_escape_percent(sql), args)
ProgrammingError: column "product" specified more than once
LINE 1: ...tus,product,severity,keywords,cc,time,changetime, product) V...
^
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than once (was: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^)
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than once
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: closed
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: fixed | Keywords:
---------------------------+--------------------
Changes (by astaric):
* status: new => closed
* resolution: => fixed
Comment:
After confirming that is solves the issue on the
[http://markmail.org/message/ndtz4kavr4hemqyg mailing list], patch was
commited in r1506070.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:11>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords, cc,
time, changetime, product) V... ^
Posted by Anze Staric <an...@gmail.com>.
> Should the same precautions be taken for UPDATE statements ?
UPDATES only change the WHERE clause (by appending the product=...),
so they should not be problematic.
> PS: Notice that tests have always passed even when product was
> duplicated in INSERTs. Indeed SQLite always used to work. At the
> moment direct tests against an instance running PostgreSQL or MySQL
> are still needed .
I have tried setting the TRAC_TEST_DB_URI to point to postgres db and
running the tests, but it did not work (every test failed). The
problem is, that reset_db tries to perform untranslated queries to the
converted database, which cause validation errors (product cannot be
null when inserting into the system table).
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords, cc,
time, changetime, product) V... ^
Posted by Olemis Lang <ol...@gmail.com>.
On 7/23/13, Anze Staric <an...@gmail.com> wrote:
> I have patched the translator so it only injects product column into
> INSERT statements, if the column was not there already. I have run all
> the tests, and they still pass. Is there anything else I should check?
> Is there a better alternative approach?
>
Should the same precautions be taken for UPDATE statements ?
PS: Notice that tests have always passed even when product was
duplicated in INSERTs. Indeed SQLite always used to work. At the
moment direct tests against an instance running PostgreSQL or MySQL
are still needed .
[...]
--
Regards,
Olemis.
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords, cc,
time, changetime, product) V... ^
Posted by Anze Staric <an...@gmail.com>.
I have patched the translator so it only injects product column into
INSERT statements, if the column was not there already. I have run all
the tests, and they still pass. Is there anything else I should check?
Is there a better alternative approach?
On Tue, Jul 23, 2013 at 10:42 AM, Apache Bloodhound
<de...@bloodhound.apache.org> wrote:
> #601: ProgrammingError: column "product" specified more than onceLINE 1:
> ...tus,product,severity,keywords,cc,time,changetime, product) V...
> ^
> ---------------------------+--------------------
> Reporter: ogaerick | Owner: nobody
> Type: defect | Status: new
> Priority: blocker | Milestone:
> Component: multiproduct | Version: 0.6.0
> Resolution: | Keywords:
> ---------------------------+--------------------
>
> Comment (by astaric):
>
> For qct, r1505666 removes product from args, so it is never added values
> dict.
> {{{
> if fname in self.values:
> }}}
> should therefore prevent it from being added to the INSERT statement.
>
> Anyway, I have attached a
> [attachment:t601_r1505871_do_not_add_product_column_if_already_exists_in_insert.diff
> patch] for sql translator, that disables injecting a product if INSERT
> statement already contains it. Can you check if applying it solves the
> issue?
>
> --
> Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:10>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+--------------------
Comment (by astaric):
For qct, r1505666 removes product from args, so it is never added values
dict.
{{{
if fname in self.values:
}}}
should therefore prevent it from being added to the INSERT statement.
Anyway, I have attached a
[attachment:t601_r1505871_do_not_add_product_column_if_already_exists_in_insert.diff
patch] for sql translator, that disables injecting a product if INSERT
statement already contains it. Can you check if applying it solves the
issue?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:10>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than once
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than once
---------------------------+---------------------
Reporter: ogaerick | Owner: astaric
Type: defect | Status: closed
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: fixed | Keywords:
---------------------------+---------------------
Changes (by astaric):
* owner: nobody => astaric
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:12>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+--------------------
Comment (by rjollos):
When I create a ticket using the quick ticket form, the following SQL is
executed (`[trac] debug_sql = true`):
{{{
04:32:59 AM Trac[dbcursor] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,product,milestone,component,version,resolution,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'prod1')
04:32:59 AM Trac[util] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,product,milestone,component,version,resolution,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'prod1')
}}}
The duplication of the `product` field, caused by the addition of the
`product` select in #569, doesn't seem to cause a problem with SQLite, but
I'll attempt to reproduce with PostgreSQL.
I'm not seeing a duplication of the `product` field for tickets created
from the `/newticket` URL (i.e. the full new ticket form):
{{{
03:46:38 AM Trac[dbcursor] DEBUG: Original SQl: INSERT INTO ticket
(summary,reporter,owner,descriobserving this
issueption,type,status,priority,milestone,component,version,keywords,cc,time,changetime)
VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s)
03:46:38 AM Trac[dbcursor] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,milestone,component,version,keywords,cc,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'@')
}}}
The latter finding isn't too surprising since there shouldn't be a product
select field within the `#inplace-propertyform` form. The product select
should only exist on the breadcrumb. Do you see a product select field in
the new ticket form when on the `/newticket` page?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords, cc,
time, changetime, product) V... ^
Posted by Ryan Ollos <ry...@wandisco.com>.
On Jul 22, 2013 8:07 AM, "Apache Bloodhound" <de...@bloodhound.apache.org>
wrote:
>
> #601: ProgrammingError: column "product" specified more than onceLINE 1:
> ...tus,product,severity,keywords,cc,time,changetime, product) V...
> ^
> ---------------------------+--------------------
> Reporter: ogaerick | Owner: nobody
> Type: defect | Status: new
> Priority: blocker | Milestone:
> Component: multiproduct | Version: 0.6.0
> Resolution: | Keywords:
> ---------------------------+--------------------
>
> Comment (by astaric):
>
> I have managed to replicate the qct problem it in postgres and commited a
> fix in r1505666. It fixes the issue for me.
>
> ogaerick, can you try the trunk version of bloodhound and see, if you
> still get the same error?
>
> --
> Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:6>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound issue tracker
Thanks, Anze. This is a fairly significant regression, and I think we
should consider including the fix in 6.1.
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+--------------------
Comment (by astaric):
I have managed to replicate the qct problem it in postgres and commited a
fix in r1505666. It fixes the issue for me.
ogaerick, can you try the trunk version of bloodhound and see, if you
still get the same error?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+--------------------
Comment (by olemis):
Replying to [comment:6 astaric]:
> I have managed to replicate the qct problem it in postgres and commited
a fix in r1505666. It fixes the issue for me.
>
> ogaerick, can you try the trunk version of bloodhound and see, if you
still get the same error?
I'm still getting the same error in PostgreSQL using both /qct and
/newticket in product context .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+--------------------
Changes (by ogaerick):
* component: dashboard => multiproduct
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than once
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than once
---------------------------+-----------------------
Reporter: ogaerick | Owner: astaric
Type: defect | Status: closed
Priority: blocker | Milestone: Release 7
Component: multiproduct | Version: 0.6.0
Resolution: fixed | Keywords:
---------------------------+-----------------------
Comment (by olemis):
related to #704
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:14>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+--------------------
Comment (by olemis):
Below I explain the reason why I'm still getting the same error this side
.
Replying to [comment:5 rjollos]:
> When I create a ticket using the quick ticket form, the following SQL is
executed (`[trac] debug_sql = true`):
> {{{
> 04:32:59 AM Trac[dbcursor] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,product,milestone,component,version,resolution,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'prod1')
> 04:32:59 AM Trac[util] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,product,milestone,component,version,resolution,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'prod1')
> }}}
>
> The duplication of the `product` field, caused by the addition of the
`product` select in #569, doesn't seem to cause a problem with SQLite, but
I'll attempt to reproduce with PostgreSQL.
>
> I'm not seeing a duplication of the `product` field for tickets created
from the `/newticket` URL (i.e. the full new ticket form):
> {{{
> 03:46:38 AM Trac[dbcursor] DEBUG: Original SQl: INSERT INTO ticket
(summary,reporter,owner,descriobserving this
issueption,type,status,priority,milestone,component,version,keywords,cc,time,changetime)
VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s)
> 03:46:38 AM Trac[dbcursor] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,milestone,component,version,keywords,cc,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'@')
> }}}
>
Unfortunately `INSERT` statements are not logged in my instance . I can
only see lines for `SELECT` statements . I'd appreciate if you share any
ideas .
> The latter finding isn't too surprising since there shouldn't be a
product select field within the `#inplace-propertyform` form. The product
select should only exist on the breadcrumb. Do you see a product select
field in the new ticket form when on the `/newticket` page?
As far as I can tell it always inserts product field twice my side . I
reproduced the sequence of invocations leading to the error in
`trac.ticket.model.Ticket` and this is what I get
{{{#!py
>>> from trac.env import open_environment as oe
>>> genv = oe('/path/to/blood-hound.net')
>>> from multiproduct.env import ProductEnvironment as PE
>>> penv = PE(genv, 'dataviz')
>>> from multiproduct.dbcursor import translate_sql
# Headless test mode ;)
>>> sql = translate_sql(penv, "INSERT INTO ticket (summary, product)
VALUES ('S', 'swlcu')")
>>> sql
u"INSERT INTO ticket (summary, product, product) VALUES ('S',
'swlcu','dataviz')"
>>> from trac.ticket.model import Ticket
>>> t = Ticket(penv)
>>> self = t
# Copy and paste lines 226-235 in trac/ticket/model.py
>>> if True:
... std_fields = []
... custom_fields = []
... for f in self.fields:
... fname = f['name']
... if fname in self.values:
... if f.get('custom'):
... custom_fields.append(fname)
... else:
... std_fields.append(fname)
...
# The query in lines 238-241
>>> orig = ("INSERT INTO ticket (%s) VALUES (%s)"
... % (','.join(std_fields),
... ','.join(['%s'] * len(std_fields))))
>>> orig
'INSERT INTO ticket (owner,type,priority,product,version) VALUES
(%s,%s,%s,%s,%s)'
>>> sql = translate_sql(penv, orig)
>>> sql
u"INSERT INTO ticket (owner,type,priority,product,version, product) VALUES
(%s,%s,%s,%s,%s,'dataviz')"
}}}
`product` appears twice because
1. it is included in `std_fields` via ITicketFieldsProvider
2. and appended once again after translation
All this happens using PostgreSQL backend .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+--------------------
Comment (by ogaerick):
I am just trying to add a ticket. Happens when I use the quick link and
press add and when I use the full form.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+--------------------
Comment (by olemis):
Replying to [comment:7 olemis]:
> Replying to [comment:6 astaric]:
> > I have managed to replicate the qct problem it in postgres and
commited a fix in r1505666. It fixes the issue for me.
> >
> > ogaerick, can you try the trunk version of bloodhound and see, if you
still get the same error?
>
> I'm still getting the same error in PostgreSQL using both /qct and
/newticket in product context .
JFTR, it seems there's an `<input type="hidden" id="field-product"
name="field_product" value="dataviz" />` element in `form#propertyform` in
/newticket page . Nevertheless, in any case backend code has to be robust
so as not to fail.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+--------------------
Comment (by astaric):
Bloodhound uses sql translation to fill in product field, based on the url
that is used to access the /newticket. Can you provide more info on what
were you doing when you encountered this error? Was this POST request done
using a specific action on the site or was it executed manually?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column "product"
specified more than onceLINE 1: ...tus, product, severity, keywords,
cc, time, changetime, product) V... ^
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#601: ProgrammingError: column "product" specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
------------------------+--------------------
Reporter: ogaerick | Owner: nobody
Type: defect | Status: new
Priority: blocker | Milestone:
Component: dashboard | Version: 0.6.0
Resolution: | Keywords:
------------------------+--------------------
Changes (by ogaerick):
* version: => 0.6.0
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/601#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker