Skip to main content
Solved

Connect to MongoDB

  • November 18, 2021
  • 3 replies
  • 95 views

I'm trying to connect to MongoDB and load data  into Timextender

I have a ODBC driver setup, and test connection works.

In Timextender I have ODBC Generic Data setup, and test connection works and to Synchronize Data Source works as well.

But when I try to execute the data transfer from MongoDB into Timextender then I get an error.

 

Best answer by Christian Hauggaard

As discussed in the support ticket, the following error messages were present:

' error: unexpected SUB at position 245

' error: unexpected STRING at position 342 near gr_notifications

A bug fix (12567) was released in 20.10.26 to handle the issue of Incorrect Accent grave sign in General ODBC setup. The Accent Grave type was character ' this has been changed to `. ODBC connections using the Accent Grave are update to use the new Single Quote.

View original
Did this topic help you find an answer to your question?

3 replies

Forum|alt.badge.img+3
  • Contributor
  • 82 replies
  • November 18, 2021

As a workaround, you may test it with CData MongoDB provider.

Creating a support ticket to follow-up on error details.


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

As discussed in the support ticket, the following error messages were present:

' error: unexpected SUB at position 245

' error: unexpected STRING at position 342 near gr_notifications

A bug fix (12567) was released in 20.10.26 to handle the issue of Incorrect Accent grave sign in General ODBC setup. The Accent Grave type was character ' this has been changed to `. ODBC connections using the Accent Grave are update to use the new Single Quote.


peter.jensen
TimeXtender Xpert
Forum|alt.badge.img+2
  • TimeXtender Xpert
  • 42 replies
  • March 18, 2025

Using TX Classic (V20.10.61) - what’s the preferred way to connect to a MongoDB ?

I have an ODBC setup, and when I sync the objects, we get a list of tables and flattened tables (which are JSON’s in the MongoDB collection).
However, when previewing such tables I often get an error - saying that some columns don’t exist.  Is there a specific ODBC driver we should use, or specific options we should set in the connection to make this work?


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings