range

I have checked other postings including Group by variable integer range using Linq but i have not found anything that is similar to my question...I am trying to group into integer ranges where the integer sequence is discontinuous. For example, if i have a set of continuous integers from 1-100 and then my set skips 101, i would want to create a record that takes the date from record #1 and #100, where the date from record #1 is the begin date and #100 is the end date. Each range of continuous integers creates a new record to add to a list of records that indicate the date at the start and end

Here goes a yet another SQL question about dates… I'm building a calendaring application using PHP and Postgres that would display events spanning days, weeks or possibly months. Each event has a start date and an end date, and selecting them by range is not a problem; however, it would be useful for me if Postgres could split multi-week events at the first day of each week. I've been told it can be done using GROUP BY and EXTRACT , but I'm not good enough with SQL to understand how. The question is: can this be done, and what would the precise query look like? Currently I'm using SELECT *

I'm using double precision floating point variables within an application I'm making. I normalize some ranges of values. Going from (for example; I've many ranges) -48.0 to 48.0 to 0.0 to 1.0 , using this simply function: double ToNormalizedParam(double nonNormalizedValue, double min, double max, double shape) { return pow((nonNormalizedValue - min) / (max - min), 1.0 / shape); } I'd like to know the differences in available and distinct values mapping from a range to another. Is there a ready-to-go function in C++? I've looked at numeric_limits , but I can't find anything useful. Is there a

I've seen several questions asking about moving cells from one workbook to another or one sheet to another using VBA, but I'm hoping to move information from one column to another in the same sheet based on specific criteria. I wrote this code to move cells from column A if they contained the word "save" to column I in the same sheet: Sub Findandcut() Dim rngA As Range Dim cell As Range Set rngA = Sheets("Jan BY").Range("A2:A1000") For Each cell In rngA If cell.Value = "save" Then cell.EntireRow.Cut Sheets("Jan BY").Range("I2").End(xlDown).Select ActiveSheet.Paste End If Next cell End Sub But,

I have a field containing an array of integers eg: _source: { ... prices: [ 20001, 30001 ] } I'd like to filter the results such that prices contains at least one of a list of values which are between eg: [20002,30000] # would not return the above document because no value is between 20002 and 30000 but [10000,20002] would return above document because 20001 in the prices field of above document is between 10000 and 20002 Elasticsearch always considers that a field can contain a list of values so, a range filter should work. If any of the values matches the range it will be filtered in. You

assigning grade on basis of range: def getGrade(size): grade ='' if size <= 32: grade = 'p4' elif size > 32 and size <=64: grade = 'p6' elif size > 64 and size <= 128: grade = 'p10' elif size > 128 and size <= 256: grade = 'p15' elif size > 256 and size <=512: grade = 'p20' elif size > 512 and size <= 1024: grade = 'p30' elif size > 1024 and size <= 2048: grade = 'p40' ...... Problem is need to add 20 more check so is there any way to do better than this approach. Due do the ranges being contiguous, you can avoid repeating the lower bound. Putting all the ranges in tuples can save you some

To access an instance of a User in a restful web-service the url is structured as shown in the curl request below: curl -v -X GET -s "$BASE_URL/User/${customer_id}.json" If I wanted to specify all User entities or page through a range of User entities, such as the first 50 Users in my database, how would I structure my request so that it is compliant with REST ??? You should start by trying to de-emphasize the meaning of the characters in a URI. While nice, pretty and readable URIs are a good thing, they have nothing to do with REST -- in fact it's a good exercise to judge the design of a