Search found 7 matches
- Tue 19 Jul 2022 06:11
- Forum: dbForge for MySQL
- Topic: Intellisense/Autocomplete for functions and procedures no longer working
- Replies: 10
- Views: 12390
Re: Intellisense/Autocomplete for functions and procedures no longer working
Thank you for the custom build - I feel special :) It works 🥳
- Mon 18 Jul 2022 07:55
- Forum: dbForge for MySQL
- Topic: Intellisense/Autocomplete for functions and procedures no longer working
- Replies: 10
- Views: 12390
- Mon 04 Jul 2022 13:23
- Forum: dbForge for MySQL
- Topic: Intellisense/Autocomplete for functions and procedures no longer working
- Replies: 10
- Views: 12390
Re: Intellisense/Autocomplete for functions and procedures no longer working
Thanks for getting back to me.
We're running many instances of MySQL 5.7. It seems to be working on Windows boxes (Windows Server 2008 R2 and MySQL 5.7.16) and not working on Linux boxes (CentOS7 and MySQL 5.7.33).
lower_case_table_names is set to 1
We're running many instances of MySQL 5.7. It seems to be working on Windows boxes (Windows Server 2008 R2 and MySQL 5.7.16) and not working on Linux boxes (CentOS7 and MySQL 5.7.33).
lower_case_table_names is set to 1
- Tue 28 Jun 2022 10:01
- Forum: dbForge for MySQL
- Topic: Intellisense/Autocomplete for functions and procedures no longer working
- Replies: 10
- Views: 12390
Intellisense/Autocomplete for functions and procedures no longer working
Hi
Since updating to version 9.0.897 (Express Edition), custom functions and procedures are no longer suggested in the autocomplete/intellisense list
Yet the following returns multiple results:
select * from mysql.proc where name like '%getarea%'
I did refresh the local cache to no avail.
Has this feature been removed from the Express Edition or is this a bug? We would love to purchase a more feature rich edition but the prices are prohibitive for most developers in 3rd world nations.
Thanks in advance and thank you for a great product.
Since updating to version 9.0.897 (Express Edition), custom functions and procedures are no longer suggested in the autocomplete/intellisense list
Yet the following returns multiple results:
select * from mysql.proc where name like '%getarea%'
I did refresh the local cache to no avail.
Has this feature been removed from the Express Edition or is this a bug? We would love to purchase a more feature rich edition but the prices are prohibitive for most developers in 3rd world nations.
Thanks in advance and thank you for a great product.
- Thu 19 Jul 2018 12:19
- Forum: dbForge for MySQL
- Topic: Page Limit in Data editor is being applied to sub queries
- Replies: 4
- Views: 2221
Re: Page Limit in Data editor is being applied to sub queries
Using the following query:
SELECT
*
FROM (SELECT
contracts.*
FROM contracts
INNER JOIN vehunits vu1
ON vu1.contract_id = contracts.id
WHERE vu1.enddatetime = 0
OR getdatetimenow() < vu1.enddatetime
LIMIT 12345) AS ContractUnits
group by ContractUnits.cmplst_id
LIMIT 5000;
Results with paginal mode enabled (194 rows):
Results with paginal mode disabled (2174 rows):
The same query in workbench returns 2174 rows:
With a subquery limit of 1000 and paginal mode disabled (194 rows):
Interestingly, the same query without the where clause does not suffer from the paginal mode issue.
SELECT
*
FROM (SELECT
contracts.*
FROM contracts
INNER JOIN vehunits vu1
ON vu1.contract_id = contracts.id
WHERE vu1.enddatetime = 0
OR getdatetimenow() < vu1.enddatetime
LIMIT 12345) AS ContractUnits
group by ContractUnits.cmplst_id
LIMIT 5000;
Results with paginal mode enabled (194 rows):
Results with paginal mode disabled (2174 rows):
The same query in workbench returns 2174 rows:
With a subquery limit of 1000 and paginal mode disabled (194 rows):
Interestingly, the same query without the where clause does not suffer from the paginal mode issue.
- Wed 18 Jul 2018 13:12
- Forum: dbForge for MySQL
- Topic: Page Limit in Data editor is being applied to sub queries
- Replies: 4
- Views: 2221
Page Limit in Data editor is being applied to sub queries
For some queries, if paginal mode is enabled, the page limit is applied to subqueries.
E.g: In the following query, even though there is a limit of 10000, a limit of 1000 is applied to the subquery.
SELECT GROUP_CONCAT(id)
FROM (
SELECT nr.id /* nr.*, getusername(nr.UsrLst_ID), a.name, a.catlst_id, cl.catagoryname*/
FROM notificationrule AS nr
INNER JOIN areaassign AS aa ON aa.id = nr.AreaAssign_ID
INNER JOIN areas AS a ON a.id = aa.Areas_id
INNER JOIN catlst AS cl ON cl.id = a.catlst_id
WHERE nr.UsrLst_ID = getuseridex('control room') AND a.catlst_id = 10
LIMIT 10000
) AS X;
But in the following similar query, it works fine:
SELECT
GROUP_CONCAT(id)
FROM (SELECT
nr.id /* nr.*, getusername(nr.UsrLst_ID), a.name, a.catlst_id, cl.catagoryname*/
FROM notificationrule AS nr
INNER JOIN areaassign AS aa
ON aa.id = nr.AreaAssign_ID
INNER JOIN areas AS a
ON a.id = aa.Areas_id
INNER JOIN catlst AS cl
ON cl.id = a.catlst_id
WHERE nr.UsrLst_ID = getuseridex('control room')
AND a.catlst_id = 10
LIMIT 10000) AS X;
SELECT
GROUP_CONCAT(id)
FROM (SELECT
*
FROM cameraconfig LIMIT 2000) AS x;
E.g: In the following query, even though there is a limit of 10000, a limit of 1000 is applied to the subquery.
SELECT GROUP_CONCAT(id)
FROM (
SELECT nr.id /* nr.*, getusername(nr.UsrLst_ID), a.name, a.catlst_id, cl.catagoryname*/
FROM notificationrule AS nr
INNER JOIN areaassign AS aa ON aa.id = nr.AreaAssign_ID
INNER JOIN areas AS a ON a.id = aa.Areas_id
INNER JOIN catlst AS cl ON cl.id = a.catlst_id
WHERE nr.UsrLst_ID = getuseridex('control room') AND a.catlst_id = 10
LIMIT 10000
) AS X;
But in the following similar query, it works fine:
SELECT
GROUP_CONCAT(id)
FROM (SELECT
nr.id /* nr.*, getusername(nr.UsrLst_ID), a.name, a.catlst_id, cl.catagoryname*/
FROM notificationrule AS nr
INNER JOIN areaassign AS aa
ON aa.id = nr.AreaAssign_ID
INNER JOIN areas AS a
ON a.id = aa.Areas_id
INNER JOIN catlst AS cl
ON cl.id = a.catlst_id
WHERE nr.UsrLst_ID = getuseridex('control room')
AND a.catlst_id = 10
LIMIT 10000) AS X;
SELECT
GROUP_CONCAT(id)
FROM (SELECT
*
FROM cameraconfig LIMIT 2000) AS x;
- Wed 18 Jul 2018 07:48
- Forum: dbForge for MySQL
- Topic: Can't set the TIME format to 24hours
- Replies: 1
- Views: 2632
Can't set the TIME format to 24hours
I can't set the 'time' format to "HH:mm:ss". It allows me to use 'hh' but not 'HH'. It does work for the datetime format.
Setting a format does not apply to the datetime selection dialog in the data editor.
Setting a format does not apply to the datetime selection dialog in the data editor.