Skip to main content



      Home
Home » Archived » EGL Development Tools » New Record From DB Generates Warning
New Record From DB Generates Warning [message #976770] Thu, 08 November 2012 15:59 Go to next message
Eclipse UserFriend
Anyone see this before?

I'm connecting to an MS SQL Database. I am creating a new record by right clicking on New --> Records --> then Create new record from database. When I select my table name and then click finish, the wizard generates a warning that states:
Cannot get valid message from column metadata
it seems to generate this for each column type of nvarchar. It also does not create those fields in the record.

Thanks,
Gregory
Re: New Record From DB Generates Warning [message #983162 is a reply to message #976770] Tue, 13 November 2012 13:33 Go to previous messageGo to next message
Eclipse UserFriend
Hi Gregory,

This is just a guess, but it sounds like your JDBC driver doesn't support returning the metadata for columns of type nvarchar. Is there a newer JDBC driver you can try out to see if this is resolved? If we're unable to determine the type for a column then we have no idea to which EGL type it should be mapped. Maybe in this case the wizard could let you manually choose the EGL types for unknown columns. If you think this would be an adequate solution, go ahead and open an enhancement request at https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EDT

-Justin
Re: New Record From DB Generates Warning [message #983314 is a reply to message #983162] Tue, 13 November 2012 16:11 Go to previous messageGo to next message
Eclipse UserFriend
Hi Justin --
I'm using the Microsoft JDBC Driver 4.0 for SQL Server that came out on 3/6/2012. Tables render properly when using the SQL Explorer plugin. It is in EDT only that this problem occurs. Any workarounds that you can think of?

Gregory
Re: New Record From DB Generates Warning [message #984407 is a reply to message #983314] Wed, 14 November 2012 12:19 Go to previous message
Eclipse UserFriend
fyi...
I added the missing fields to my record as string fields, then I used the CAST command in the select statement, e.g. CAST(id as varchar(80)). That allowed me to get past the error.
Previous Topic:EDT 0.8.2 Milestone 3 is here!
Next Topic:How can I manage widget instances?
Goto Forum:
  


Current Time: Sun Jun 22 02:23:40 EDT 2025

Powered by FUDForum. Page generated in 0.24135 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top