Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 3 of 3 total |
EDB doesn't like it.. |
Mon, Sep 10 2018 11:55 PM | Permanent Link |
Ian Branch | Hi Team,
How come the following falls over at the '.category'? {sql} select * from configuration.logevents where (upper(configurtion.logevents.category) like 'INFO%') order by logtimestamp {sql} Regards & TIA, Ian |
Tue, Sep 11 2018 2:09 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Ian
How about because its wrong This "configurtion.logevents.category" would (I think) break down to session.database.column and that's not allowed in ElevateDB. You're allowed database.table and table.column. You have a number of choices select * from configuration.logevents where (upper(logevents.category) like 'INFO%') order by logtimestamp or select * from configuration.logevents where (upper(category) like 'INFO%') order by logtimestamp You could use an alias eg select * from configuration.logevents X where (upper(lX.category) like 'INFO%') order by logtimestamp Finally - there's no need for the UPPER since in the table category is defined as Category" VARCHAR(15) COLLATE "ANSI_CI", so my preferred format would be select * from configuration.logevents where category like 'INFO%' order by logtimestamp Roy Lambert |
Tue, Sep 11 2018 3:33 AM | Permanent Link |
Ian Branch | Roy Lambert wrote:
> This "configurtion.logevents.category" would (I think) break down to session.database.column and that's not allowed > in ElevateDB. You're allowed database.table and table.column. Hi Roy, Now it makes perfect sense. Thank you. Regards, Ian |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |