Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Invalid column name 'summary'

web-app

I am receiving an invalid column name error when I try to view an issue details or view a list of issues in the components of some projects. I was running v3.5.4 and on the forum found some other people with similar issues (although not the same column name) where the advise was to upgrade to the latest version.

I have upgraded to v3.6.2 as per the instructions but still get the same error, everything else appears to work (in MSIE, in Firefox, the top menu (Home, Projects, Create Issue, Administration doesn't work - shows as bullet points).

martin
· 1
martin
Replies (10)
helpful
0
not helpful

Can you please post the stack trace?

Also, did you run create_view.sql.

 

As for the menu, did you re-install the web app? Aer you using the old conifg file?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Oops - meant to post the trace:

Invalid column name 'summary'. at CounterSoft.Gemini.DataProvider.x4f26f7a726757349.xd8280387c605aca4(CustomFieldEN x5a09e7cd54476202, Int32 xb378eaa6f96e5474) at CounterSoft.Gemini.DataProvider.x4f26f7a726757349.xd8280387c605aca4(CustomFieldEN x5a09e7cd54476202) at CounterSoft.Gemini.Business.xa07794653f9cfd6c.xefdacb58f6369971() at CounterSoft.Gemini.Web.Issue.ViewIssue.PageLoad(Object sender, EventArgs e) at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

I did run create
view.sql and it appeared to run successfully.


martin
· 1
martin
helpful
0
not helpful

I did the full upgrade, including the web-app. I am using the new config file. I removed all the old v3.5.4 files from the directory before copying in the new ones to make sure that there were no old remanents left behind.


martin
· 1
martin
helpful
0
not helpful

Ok, the problem is with your custom field definition. You seem to have a custom field that is bound to a lookup table and summary used to be a field in that lookup. Please check your definition under the Administration -> Custom Fields.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Ah - makes sense now.  I have removed that custom field and all now works. What I was trying to do was get a simple list of values in a lookup field from a table within the Gemini database. I know the principle behind the lookup field but can't get the actual lookup to work.


martin
· 1
martin
helpful
0
not helpful

Which table are you trying to use?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

A custom table called domain_users which has the following fields: NTUsername, Firstname, Lastname and Email. I really just want to populate a listbox with all the NTUsername's from the table.


martin
· 1
martin
helpful
0
not helpful

I would create a new field (Fullname) that will be the Firstname + ' ' + Lastname and
create a custom field and populate the lookup fields (the table should be in the Gemini database):

  • Lookup table name: domain_users
  • Lookup key field name: NTUsername
  • Lookup description field name: Fullname
  • Lookup sort field name: Fullname


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Hmm... no luck really - just get "invalid column name" errors. I am going to leave this for now - all I really want to do is return all values from a particular column in the table.

A future addition to Gemini that would be really good, would be the ability to have a drop-down box that is populated via a custom entered SQL statement. So instead of having the four options: "Lookup table name", "Lookup key field name", "Lookup description field name" and "Lookup sort field name", you would just have "Enter SQL Statement". That would give not only the benefit of current lookups, but also lookups based on hard coded parameters or statements with no WHERE clause.


martin
· 1
martin
helpful
0
not helpful

Mark Wing
· 9108
Mark Wing