Comment Re:Toxic (Score 1) 204
I only use ceramic non-stick or all steel pots. I hope they have something more than "all aluminum" or it's at least coated with another non-toxic material.
Let me guess, you don't get vaccinated, either...
I only use ceramic non-stick or all steel pots. I hope they have something more than "all aluminum" or it's at least coated with another non-toxic material.
Let me guess, you don't get vaccinated, either...
Are you just as histrionic over Lois Lerner's missing emails?
That was awful. Pick up just about any Harry Turtledove book for a more thoughtful take on the subject.
You need one of those gay European man purses to carry around all your loose change. Then it makes sense, I suppose.
I do want the string built in Sequence Order.
Here's the weird thing- query #2 has been working for 4 months. Not sure what changed, but the explanation that the rows are being fetched slow makes sense (they're always messing with my server settings!).
The Top 800 is included in the subquery because MS SQL returns an error without it- Can't use an Order By in a subquery without a TOP. 800 just happens to be ~5x the current number of Model Points in the Model Points Table (and thus, this function should NEVER return that many rows).
I thought the table valued function call was already doing that, but that does point to an answer- perhaps it's only fetching the one row before evaluating the concatenation.
I didn't explain the behavior adequately.
SELECT * FROM dbo.GetReferencedModelPointsByJobID(@JobID)
Returns someplace between 2-56 rows, depending on JobID
The second query does NOT error out, but is not returning a comma delimited string of all rows, but instead, in some cases, is returning only ONE row.
Since I'm using this to build a temp table, it doesn't error out until I attempt to fill columns in the temp table that do not exist.
That I'm running a risk with the first of > 800 Model Points, but in my database, I never exceed 80 modelpoints for a given job ID.
But I still don't understand why the subquery is necessary (in some cases).
I have a Table Valued Function that returns a simple parameterized view. I want to turn that view into a string.
Can anybody tell me why the first query works and the second one doesn't?
DECLARE @JobID INT
DECLARE @strOut VARCHAR(MAX)
SET @JobID=2861
To this day, males 18+ must register. Those who do not cannot receive Federal financial aid, nor work as a GS or contract employee for the Fed.
Did it do a 4G inverted dive?
I wish I could mod this up.
I recently learned Microsoft MVC, being an old application programmer. Once I grasped the concept, I ended up with three competing database models to the same bloody schema in SQL Server, because some controls use AJAX/Entity Framework, others JSON/SQLDataObject, still others a SQLClient loaded on page load.
I got it to work, but what a rube goldberg machine it is, complete with the maintenance headache that implies.
I invented the "One Click" wheel.
Pfft. I invented the wheel with round corners.
But what it really means is that with this news getting out, Al Qaida is going to start manufacturing cell phone batteries that are half battery (to power up the device and show that it works) and half C4 (bonus, detonation circuit attached to the charger).
Always draw your curves, then plot your reading.