Help or Manual
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Help or Manual
We are currently working on completing the help file for PrimalSQL and we are sorry for any inconvenience. If you have any questions, please feel free to post them.
Thank you,
David
Thank you,
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Help or Manual
Thanks David,
I was looking for a way to modify the key words for the SQL dialects. Specifically, the join syntax of the product we access (Providex) through the ODBC driver places the join in curly brackets, and begins with "oj" whether it is an inner or outer join.
When I have the dialect selected automatically, PrimalSQL 2009 selects universal, which does not match the join syntax I need.
I have found that the join syntax is similar to MySQL, where the key word "oj" is included for compatibility with ODBC data sources. I have tried to use the several MySQL dialects, but they do not see my data.
I realize I can manually edit the sql statements generated, I was just hoping there was a way to get the syntax fully automated.
Thank you.
I was looking for a way to modify the key words for the SQL dialects. Specifically, the join syntax of the product we access (Providex) through the ODBC driver places the join in curly brackets, and begins with "oj" whether it is an inner or outer join.
When I have the dialect selected automatically, PrimalSQL 2009 selects universal, which does not match the join syntax I need.
I have found that the join syntax is similar to MySQL, where the key word "oj" is included for compatibility with ODBC data sources. I have tried to use the several MySQL dialects, but they do not see my data.
I realize I can manually edit the sql statements generated, I was just hoping there was a way to get the syntax fully automated.
Thank you.
Help or Manual
You do have the option to change the dialect on the Query Builder. Click on the "Query Builder Properties" button on the Ribbon bar and go to the "Non-Visual Options" tab where you can select the desired dialect.
Please note that the dialect is store with the query file and not the connection.
David
Please note that the dialect is store with the query file and not the connection.
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Help or Manual
Sorry you wish to tweak the existing dialect to provide a keyword? You can customize the Builder in a few ways, but you can't change the actual words, unless it is already provided in an existing dialect.davidc2009-04-29 09:57:27
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.