171 results found

1. Shortcut to move commas from start to end and vice versa.

   I would like to only affect the placement of commas in a column list, without applying other formatting options. This would work similar to Ctrl-B, Ctrl-B to remove brackets or Ctrl-B, C to insert semicolons, in that no other formatting would take place.

   There are times I have a rather well-formatted script but it has been written with commas at the start of the line and I prefer them at the end. A new shortcut would toggle placing commas at the start or end of the line without affecting other formatting within the script.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Make parentheses rules customizable (where what applies) instead of a global setting

   I have different wants for parentheses rules: Collapse short content or not, Having Parentheses on separat lines or leading the content, etc. It all depends on the context. But currently the setting is global.

   I would like to be able to define one rule for, say, Primary Key definitions, and another rule for, say, the columns of a table.
   I would want one thing for Control Flow sections, and another thing for Variables declarations.

   Today, I need to choose which one to be dominant (or stop using FORMAT SQL on the entire script, but just highlight the block where I want the formatting to occur). It would be a huge time-saver, if I could just format everything every time, without FORMAT SQL command messing up various places.

   I have different wants for parentheses rules: Collapse short content or not, Having Parentheses on separat lines or leading the content, etc. It all depends on the context. But currently the setting is global.

   I would like to be able to define one rule for, say, Primary Key definitions, and another rule for, say, the columns of a table.
   I would want one thing for Control Flow sections, and another thing for Variables declarations.

   Today, I need to choose which one to be dominant (or stop using FORMAT SQL on the entire script, but just highlight the block where I… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Separate "Collapse parentheses if contents are shorter than..." option from Primary Keys

   In SQL Prompt, Formatting Styles, I would like to differentiate the “Short parentheses contents” behavior, so it didn’t impact the primary key when I add a Constraint Primary Key Clustered at Create Table time.
   I like my PK fields to stand out, not hide in a block of text.
   But I also like any other listing of a few fields to be kept on a single line, and not bloating the screen for no reason at all.
   Currently, I can’t have both.

   In short, I want

   CREATE TABLE dbo.Orders
   (
   OrderDate DATETIME NOT NULL,
   OrderID INT NOT NULL,
   CustomerID INT NULL,
   CONSTRAINT PKOrders
   PRIMARY KEY CLUSTERED (
   OrderDate ASC,
   OrderID ASC
   )
   WITH (PADINDEX = OFF, STATISTICSNORECOMPUTE = OFF, IGNOREDUPKEY = OFF, ALLOWROWLOCKS = ON,
   ALLOWPAGE_LOCKS = ON
   ) ON [PRIMARY]
   ) ON [PRIMARY];

   instead of this:

   CREATE TABLE dbo.Orders
   (
   OrderDate DATETIME NOT NULL,
   OrderID INT NOT NULL,
   CustomerID INT NULL,
   CONSTRAINT PKOrders
   PRIMARY KEY CLUSTERED (OrderDate ASC, OrderID ASC)
   WITH (PADINDEX = OFF, STATISTICSNORECOMPUTE = OFF, IGNOREDUPKEY = OFF, ALLOWROWLOCKS = ON,
   ALLOWPAGE_LOCKS = ON
   ) ON [PRIMARY]
   ) ON [PRIMARY];

   In SQL Prompt, Formatting Styles, I would like to differentiate the “Short parentheses contents” behavior, so it didn’t impact the primary key when I add a Constraint Primary Key Clustered at Create Table time.
   I like my PK fields to stand out, not hide in a block of text.
   But I also like any other listing of a few fields to be kept on a single line, and not bloating the screen for no reason at all.
   Currently, I can’t have both.

   In short, I want

   CREATE TABLE dbo.Orders
   (
   OrderDate DATETIME NOT NULL,
   OrderID INT NOT NULL,
   CustomerID INT… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Multiple format options for insert statements

   Currently SQL Prompt only has one option for formatting insert statements which poses a problem for us with multi value set inserts.

   Ideally we'd be able to select a formatting for a single value set insert and another format for a multi value set insert.

   This would allow us to do something like this:

   -- Single Value Set Insert
   INSERT INTO TestTable (TestName,
   ~~~~TestValue,
   ~~~~TestDate)
   VALUES (N'Something',
   ~~~~140,
   ~~~~'1/1/2019')

   -- Multi Value Set Insert
   INSERT INTO TestTable (TestName, TestValue, TestDate)
   VALUES (N'Something', 140, '1/1/1900'),
   ~~~~(N'SomethingElse', 150, '1/2/1900'),
   ~~~~(N'SomethingElse2', 160, '1/2/2000')

   The issue for us is that we have need of the single value set insert format in our stored procedures and most of our normal code as it allows for only one direction of scrolling (up/down instead of up/down and side to side).
   
   But in some population and testing scripts we really need the multi value set insert format (or something close to it) to prevent the scripts from being ridiculously long and for ease of identifying where one value set ends and another starts.

   It would be great if SQL Prompt gave us support for this.

   Currently SQL Prompt only has one option for formatting insert statements which poses a problem for us with multi value set inserts.

   Ideally we'd be able to select a formatting for a single value set insert and another format for a multi value set insert.

   This would allow us to do something like this:

   -- Single Value Set Insert
   INSERT INTO TestTable (TestName,
   ~~~~TestValue,
   ~~~~TestDate)
   VALUES (N'Something',
   ~~~~140,
   ~~~~'1/1/2019')

   -- Multi Value Set Insert
   INSERT INTO TestTable (TestName, TestValue, TestDate)
   VALUES (N'Something', 140, '1/1/1900'),
   ~~~~(N'SomethingElse', 150, '1/2/1900'),
   ~~~~(N'SomethingElse2', 160, '1/2/2000')

   The issue for us is that we have need of… more

   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Format lists on a clause basis

   I would like to control the list behavior on a clause by clause basis so that I can separate the formatting on my DECLARE statements differently than lists within SELECT and INSERT statements. As it stands, these are conflicting changes. So, the only way to get each variable declared on a separate line is to also have every column in other statements on a separate line. I'd like to be able to do BOTH of these:

   DECLARE @GUID UNIQUEIDENTIFIER = NEWID(),
   @Char CHAR(1) = 'A',
   @Int INT = 1,
   @Datetime DATETIME = CURRENTTIMESTAMP,
   @Decimal DECIMAL(18,10) = 1.0,
   @Date DATE = CURRENTTIMESTAMP,
   @Time TIME = CURRENT_TIMESTAMP,
   @Bit BIT = 1,
   @Money MONEY = 1.00,
   @Binary VARBINARY(18) = 0x01,

   INSERT INTO Test.Test
   (ID, Code, Description, Name, ExternalID, CreatedBy, CreatedUTC, LastUpdateBy, LastUpdateUTC, RowVersion,
   DLLoadDate, ServerExecutionID
   VALUES (@Int, @Char, @Char, @Char, @Char, @Char, @Datetime, @Char, @Datetime, @Binary, @Datetime, @Int)

   I would like to control the list behavior on a clause by clause basis so that I can separate the formatting on my DECLARE statements differently than lists within SELECT and INSERT statements. As it stands, these are conflicting changes. So, the only way to get each variable declared on a separate line is to also have every column in other statements on a separate line. I'd like to be able to do BOTH of these:

   DECLARE @GUID UNIQUEIDENTIFIER = NEWID(),
   @Char CHAR(1) = 'A',
   @Int INT = 1,
   @Datetime DATETIME = CURRENTTIMESTAMP,
   @Decimal DECIMAL(18,10) = 1.0,
   @Date DATE… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Custom values for VALUES clause

   I write a LOT of unit tests, usually at the rate of 15:1 to 20:1 to my executing code. I have these standardized and templated to make them easier and more consistent to build. e.g. @GUID UNIQUEIDENTIFIER = NEWID(),
   @Char CHAR(1) = 'A',
   @Int INT = 1,
   @Datetime DATETIME = CURRENTTIMESTAMP,
   @Decimal DECIMAL(18,10) = 1.0,
   @Date DATE = CURRENTTIMESTAMP,
   @Time TIME = CURRENT_TIMESTAMP,
   @Bit BIT = 1,
   @Money MONEY = 1.00,
   @Binary VARBINARY(18) = 0x01,

   These go into my VALUES clause for INSERT statements, but I current have to do all of this manually, which takes a LOT of time when you're writing several thousand of these every single week. What I'd like to do is configure SQL Prompt to use my custom set instead of default values when it generates an INSERT statement.

   So instead of seeing:
   VALUES (0, -- ID - int
   N'' , -- Code - nvarchar(256)
   SYSDATETIME(), -- CreatedUTC - datetime2(7)
   NULL, -- RowVersion - varbinary(18)

   I'd like to see
   VALUES (@Int, -- ID - int
   @Char, -- Code - nvarchar(256)
   @Datetime, -- CreatedUTC - datetime2(7)
   @Binary, -- RowVersion - varbinary(18)

   I write a LOT of unit tests, usually at the rate of 15:1 to 20:1 to my executing code. I have these standardized and templated to make them easier and more consistent to build. e.g. @GUID UNIQUEIDENTIFIER = NEWID(),
   @Char CHAR(1) = 'A',
   @Int INT = 1,
   @Datetime DATETIME = CURRENTTIMESTAMP,
   @Decimal DECIMAL(18,10) = 1.0,
   @Date DATE = CURRENTTIMESTAMP,
   @Time TIME = CURRENT_TIMESTAMP,
   @Bit BIT = 1,
   @Money MONEY = 1.00,
   @Binary VARBINARY(18) = 0x01,

   These go into my VALUES clause for INSERT statements, but I current have to do all of this manually, which takes a LOT… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Automatically add DROP TABLE IF EXISTS for #temp tables

   It would be nice if SQL Prompt had a way to add in the code DROP TABLE IF EXISTS #table for temp tables. Ideally it would add the statement immediately before the table is created from a CREATE TABLE or SELECT INTO statement.

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Add option to wrap lines when concatenating strings

   Sometimes I set a variable equal to many strings concatenated together using the "+" syntax. When I format with Regdate, there is no option to wrap lines in this case. Everything ends up on the same line as the SET, so the lines often get very wide and go off screen.
   It would be great if there was an option to wrap text if things got too wide horizontally.
   One solution would be a setting to format concatenated strings like this:
   SET @Variable = N'String1'
   + N'String2'
   + N'String3'

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   AdminTim Dalton (Product Manager, Redgate) responded

   Hi Amanda,

   Would the ‘wrap lines longer than X characters’ option in the formatting styles help with this?

   Tim

9. Closing parenthesis and content indention on APPLY/EXISTS not indenting

   It seems that the contents and closing parenthesis of EXISTS and APPLY clauses is not being indented as I would expect. So either i'm weird....or Format SQL is doing it wrong?

   I'm using (
   .....this parentheses style
   )

   What it's doing:

   SELECT *
   FROM tblA a
   WHERE 1 = 1
   .....AND EXISTS (
   .....SELECT *
   .....FROM tblB b
   .....WHERE b.Col1 = a.Col1
   ..........AND b.Col2 = a.Col2
   ..........AND b.Col3 = a.Col3
   )

   What I expect:

   SELECT *
   FROM tblA a
   WHERE 1 = 1
   .....AND EXISTS (
   ..........SELECT *
   ..........FROM tblB b
   ..........WHERE b.Col1 = a.Col1
   ...............AND b.Col2 = a.Col2
   ...............AND b.Col3 = a.Col3
   .....)

   It seems that the contents and closing parenthesis of EXISTS and APPLY clauses is not being indented as I would expect. So either i'm weird....or Format SQL is doing it wrong?

   I'm using (
   .....this parentheses style
   )

   What it's doing:

   SELECT *
   FROM tblA a
   WHERE 1 = 1
   .....AND EXISTS (
   .....SELECT *
   .....FROM tblB b
   .....WHERE b.Col1 = a.Col1
   ..........AND b.Col2 = a.Col2
   ..........AND b.Col3 = a.Col3
   )

   What I expect:

   SELECT *
   FROM tblA a
   WHERE 1 = 1
   .....AND EXISTS (
   ..........SELECT *
   ..........FROM tblB b
   ..........WHERE b.Col1 = a.Col1
   ...............AND b.Col2 = a.Col2
   ...............AND… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Indent AND/OR in WHERE/GROUP BY/etc. differently than ON clause

    Support request #137199: Provide an option to indent AND/OR entries in a WHERE clause to line up indented, but leave AND/OR entries directly underneath ON clauses:

    SELECT
            t1.col5
            , t2.col6
    FROM
            table1 t1
            INNER JOIN table2 t2
                    ON t1.col1 = t2.col1
                    AND t1.col2 = t2.col2 -- AND is directly below ON clause
    WHERE
            t1.col3 = 'Test'
            AND t2.col4 = 5 -- AND is indented underneath WHERE

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. format Window functions

    SQL Prompt fails badly in formatting window functions. As these are present at least since SQL 2014, SQL Prompt should be able to interpret them and format them accordingly.

    Example:

    I would format the LAG() function as follows:

    SELECT
    myColumn AS realColumn
    ,LAG(myColumn, 1, 0)
    OVER (
    PARTITION BY someColumn
    ORDER BY anotherColumn) AS calculatedColumn

    Try this with SQL Prompt - it's result is not very nice...

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. format expressions like operator

    Would it be possible to treat the 'LIKE' operator the same as '=' in the Expressions\Operators settings so they are all aligned?

    select AddressID
    from Person.Address
    where ModifiedDate
    between dateadd(month, -6, getdate())
    and getdate()
    and City = 'Bothell'
    or left(PostalCode, 2) like 'CB%'
    or PostalCode = @prefix + @suffix

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Make equals signs line up with tabs

    When I type code I like to line up all the equals (=) signs using tabs so that all the code to the right of the equals sign lines up nicely on my screen. I find this really useful for improving readability when using column aliases, in joins, and in update statements.
    I can't find an option in SQL Prompt to do this and it annoys me when I format my SQL and all the equals signs become ragged.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Lists formatting for Columns and Parameters should be treated separately

    The starting item in a List of Columns for a SELECT statement is fine to place on the same line as the SELECT, however, for EXEC <proc name that is probably longer> it looks odd to have the Parameters line up at the end. This should be a separate choice for EXEC Parameters. I chose the "commas before" style for most everything, but prefer the "default" layout for EXEC proc parameters.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Refactoring INSERT into MERGE

    Refactoring INSERT into UPDATE is definitely useful, but most of us are familiar with these. The complex MERGE statement is a mess, and a clean way to generate that would be fantastic!! Especially since you can figure out the primary keys, etc..

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Formatting arithmetic - new lines (Apex has this)

    The only edge Apex has over SQL Prompt formatting, at least for my use, is being able to organize long equations. If I am using a large number of columns for an equation, I'd like to place each new column on a new line.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Top with parenthesis should be a formatting option

    Changing

    SELECT TOP 10...

    to

    SELECT TOP (10)... should be a formatting option.

    11 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Align BETWEEN with comparison operators

    It's currently possible to align operations in WHERE which is great, but BETWEEN is not aligned.
    Example - currently:
    WHEREModifiedDate BETWEEN DATEADD(MONTH, -6, GETDATE()) AND GETDATE()
    AND City__________= 'Bothell'
    OR LEFT(PostalCode, 2)= 'CB'
    OR PostalCode_______= @prefix + @suffix

    Expected:
    Example - currently:
    WHEREModifiedDate_BETWEEN DATEADD(MONTH, -6, GETDATE()) AND GETDATE()
    AND City________= 'Bothell'
    OR LEFT(PostalCode, 2)= 'CB'
    OR PostalCode_______= @prefix + @suffix

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Move the Options - Styles configuration to the individual Style definition page

    Options - Styles pane contains, for example, "Apply column alias style" and its drop-down. This does not belong as a universal style setting, among others.

    Please move it to the "Formatting Styles" configuration dialog.

    This is because many practitioners either do not know about the "alias = column" capability in T-SQL, or don't like it, or it's contrary to company standards. The ability to use this form, which IMO is more brain-friendly, ought to be on the Formatting page as it is, in fact, a significant style element.

    Thanks.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. open source sql prompt's formatting module.

    open source sql prompt's formatting module.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close