Few question about new features and current functionality

5 Posts
2 Users
0 Likes
140 Views
(@mikulka)
Member
Joined: 3 months ago
Posts: 7
Topic starter  

1. Are you planing to add support for PostgreSQL plpgsql language ?

2. It would be great if you add atleast PERFORM command ( in fact alias SELECT)
https://www.postgresql.org/docs/16/plpgsql-statements.html.

3. And I had one strange issue with Justify right on Profile 1 - Destop App.
From some point I wasn't able to force this option to work.
I tried "the same" setting on Profile 2 and it is functional.
ResetProfile has no influence, still Justify right not work on Profile 1.

image

4. It would be great if you will add possibility in Right justify to format code AS example below ...

-- line comment
SELECT dept_nbr ,
   dept_name ,
   employee_name ,
    MAX (salary_amount)
  FROM dept
  LEFT OUTER JOIN employee ON dept.dept_nbr = employee.dept_nbr
 RIGHT OUTER JOIN orders ON order_nbr = dept_nbr
 INNER JOIN salary ON dept_name = salary_name
 WHERE
/*
block comment line 1
block comment line 2
*/
dept.dept_name = employee.dept_name
   AND dept_nbr = 'A4711'
   AND dept_name = 'Consultants'
 ORDER BY dept_nbr ,
    employee_nbr
 GROUP BY
This topic was modified 3 months ago by Mikulka

   
Quote
(@mikulka)
Member
Joined: 3 months ago
Posts: 7
Topic starter  

To point 3. I delete Profile 1 files on disk and recreate profile 1 and now works well.


   
ReplyQuote
Guido
(@admin)
Member Admin
Joined: 2 years ago
Posts: 175
 

@mikulka thank you very much for your feedback. I am working on new features for February Release. The update is concentrating on SQL formatting and adding more precise formatting features regarding linebreaks for commas in INSERT, UPDATE statements.

I could also add new keywords for PostgreSQL plpgsql language.

Will check the info on https://www.postgresql.org/docs/16/plpgsql-statements.html.

Again, thanks for your feedback. It is this kind of feedback which makes the formatter better and better knowing there are so many different formatting options still not realised because sql & plsql parsing is really a big job.

 

Regards

Guido

 


   
ReplyQuote
(@mikulka)
Member
Joined: 3 months ago
Posts: 7
Topic starter  

@admin Thank you very much for quick answer.
Meanwhile I was waiting for an answer, that was very fast by the way,  I found solution for point 4.
SQL Idention Large Keyword size
made the magic I wanted - looks well for my needs.
I understand that plpgsql is big task.
Anyway your formatting is the best formatter what I found on NET.
I am looking forward for next versions.
Wish You all good

Michal


   
ReplyQuote
Guido
(@admin)
Member Admin
Joined: 2 years ago
Posts: 175
 

@mikulka 😀


   
ReplyQuote
Share: