Comments
Sort by recent activity
This issue still exists in 3.8.0.244, where you have to have spaces between the operator and the objects you are comparing for candidates to work properly.
This does not work:
SELECT *
FROM MASTER.dbo.spt_values msp
WHERE 1<>msp.<cursor>
While this does:
SELECT *
FROM MASTER.dbo.spt_values msp
WHERE 1 <> msp.<cursor>
The other operators I have found to suffer from requiring a space after them before the suggetions work are:
>
<
!>
!<
Michael / comments
This issue still exists in 3.8.0.244, where you have to have spaces between the operator and the objects you are comparing for candidates to work properly.
This does not work:
SELECT *
FROM MASTER....
I already have both options set how you specify. The Column Name joining turned on, and the case-sensitive filtering turned off, and it still isn't suggesting a join. / comments
I already have both options set how you specify. The Column Name joining turned on, and the case-sensitive filtering turned off, and it still isn't suggesting a join.
It looks like 3.8.0.244 doesn't fix two of the issues I reported:
SELECT
CAST(NULL AS NUMERIC(16,0)) AS tdl_id,
tx_id,
post_date,
plan_id,
c.payor_id
INTO #DetailsForCredit
FROM edic_details n
LEFT JOIN Edic.dbo.COVERAGE c
ON n.CUR_CVG_ID=c.COVERAGE_ID;
SELECT * FROM #DetailsForCredit
WHERE #DetailsForCredit.<cursor>
Once you have typed the . right before <cursor> the suggestion box pops up with what you would expect, but does not include the payor_id field. It appears that by using the "c." alias in front of the field name that the field gets excluded from the suggestions.
SELECT tx_id
INTO #test3
FROM edic_charges
UNION ALL
SELECT tx_id FROM edic_details;
SELECT * FROM #test3 WHERE #test3.<cursor>
After you hit the . it doesn't bring up any suggestions. If you take the UNION ALL part out it works OK. I don't know how many people use UNION <ALL> as part of a SELECT .. INTO statement, but I suspect not many, so it probably isn't a big deal.
Michael / comments
It looks like 3.8.0.244 doesn't fix two of the issues I reported:
SELECT
CAST(NULL AS NUMERIC(16,0)) AS tdl_id,
tx_id,
post_date,
plan_id,
c.payor_id
INTO #DetailsForCredit
FROM edic_details n
LEFT...
Another small item I found is that a sort of 'rare' SELECT INTO query isn't recognized:
SELECT tx_id
INTO #test3
FROM edic_charges
UNION ALL
SELECT tx_id FROM edic_details;
SELECT * FROM #test3 WHERE #test3.<cursor>
After you hit the . it doesn't bring up any suggestions. If you take the UNION ALL part out it works OK. I don't know how many people use UNION <ALL> as part of a SELECT .. INTO statement, but I suspect not many, so it probably isn't a big deal. / comments
Another small item I found is that a sort of 'rare' SELECT INTO query isn't recognized:
SELECT tx_id
INTO #test3
FROM edic_charges
UNION ALL
SELECT tx_id FROM edic_details;
SELECT * FROM #test3 WHE...
Another temp table related problem... Given these statements:
SELECT
CAST(NULL AS NUMERIC(16,0)) AS tdl_id,
tx_id,
post_date,
plan_id,
c.payor_id
INTO #DetailsForCredit
FROM edic_details n
LEFT JOIN Edic.dbo.COVERAGE c
ON n.CUR_CVG_ID=c.COVERAGE_ID;
SELECT * FROM #DetailsForCredit
WHERE #DetailsForCredit.<cursor>
Once you have typed the . right before <cursor> the suggestion box pops up with what you would expect, but does not include the payor_id field. It appears that by using the "c." alias in front of the field name that the field gets excluded from the suggestions. / comments
Another temp table related problem... Given these statements:
SELECT
CAST(NULL AS NUMERIC(16,0)) AS tdl_id,
tx_id,
post_date,
plan_id,
c.payor_id
INTO #DetailsForCredit
FROM edic_details n
LEFT JOI...
This still hasn't been fixed in 3.8.0.244, but I am able to narrow it down to the ON candidates are not honoring my option of ignoring the case of the field names. (The field is in all upper case in the table.)
Michael / comments
This still hasn't been fixed in 3.8.0.244, but I am able to narrow it down to the ON candidates are not honoring my option of ignoring the case of the field names. (The field is in all upper case i...
I agree. It's not anything critical, and I certainly wouldn't want to hold up the 3.6 release for it, so just stick it somewhere on the "possibly in the future" list.
Thanks for all the quick help! / comments
I agree. It's not anything critical, and I certainly wouldn't want to hold up the 3.6 release for it, so just stick it somewhere on the "possibly in the future" list.
Thanks for all the quick help!
OK, that makes sense. (Maybe I should RTFM, or explore the options a little more.)
I tried adding "," or ", " as a trigger word, but it doesn't appear to work. I'm not sure I would always want it to be a trigger anyhow, I would only want it to trigger when adding a field to a select statement probably. Probably not in a function or IN() clause, etc.
It isn't that big of a deal, I can start typing or hit ctrl-space, but it would be nice. / comments
OK, that makes sense. (Maybe I should RTFM, or explore the options a little more.)
I tried adding "," or ", " as a trigger word, but it doesn't appear to work. I'm not sure I would always want it t...
I was being lazy and re-used the same example as last time, so try this one: (the INTO part has nothing to do with the behavior.)
Given this query:
SELECT DISTINCT
tdl_id<cursor1>
FROM edic_cga_details<cursor2>;
If at <cursor1> location I type ", " nothing happens, until I start to type a field name. On the other hand if at <cursor2> location I type "WHERE " a suggestion pop-up immediately comes up. Same happens when adding and AND to the where. / comments
I was being lazy and re-used the same example as last time, so try this one: (the INTO part has nothing to do with the behavior.)
Given this query:
SELECT DISTINCT
tdl_id<cursor1>
FROM edic_cga_det...
Cool, thanks!
And could you share what ever you have that allows you to create time? [image]
(It must have been easier than you originally thought if it took less than a half hour to add.) / comments
Cool, thanks!
And could you share what ever you have that allows you to create time?
(It must have been easier than you originally thought if it took less than a half hour to add.)