The ambiguity actually comes in to play because προσκαρτεροῦντες is a present participle. The present tense has so many different categories, such as descriptive, iterative, durative, tendential, historical, futuristic that there is some ambiguity. These categories come from a perceived need to f...
@swasheck is 'pray continually' a single word? I think that is what you are saying.
Presumably you are not suggesting that Paul was definitely not speaking 'superlatively' - just that translation issues make it hard to be sure?
In other places it does seem Paul is happy to use superlatives, eg 1 Thess 3:10
perhaps even that is arguable - but cf 1 Thess 2:9
@JonEricson pray is not a verb in this context --- it's a dative noun
the verbs are "were" and "continuing" ... the present is confusing because you have a participle that claims to be present ... AND the word meaning is "continuing" so certainly there MUST be an ongoing/durative intent behind this
@JackDouglas ... incoming postgresql question ... i may not be going about this the proper way (in any capacity - theory or otherwise) so feel free to correct me
i'm wanting to provide visual cues for words in a text (like all verbs of a particular tense are background red, etc.)
so i'm splitting a string on a space and then unnesting them
then i have a function that will get the specific details for that word
the following is the best set-based way i have found, so far
with words as
(select unnest(string_to_array(analysis_text,' ')) as word from verse where version_id = 3 and searchref between 857 and 879 order by version_id, id)
select (worddetailsbyword(word)).*
from words
it takes 85 seconds
this is a python parsing nightmare but takes 6 seconds
with words as
(select unnest(string_to_array(analysis_text,' ')) as word from verse where version_id = 3 and searchref between 857 and 879 order by version_id, id)
select worddetailsbyword(word)
from words
just doing this
select unnest(string_to_array(analysis_text,' ')) as words from verse where version_id = 3 and searchref between 857 and 879 order by version_id, id
and then iterating through and calling the function for each word in python is about 8 seconds
soooooooooooooo ... i'm assuming that there's not really a way to index on this function that joins a bunch of tables ...
ok ... done babbling
it may just be that i'm trying to do too much all at once
select count(*) from ( with words as (select unnest(string_to_array(analysis_text,' ')) as word from verse where version_id = 3 and searchref between 857 and 879 order by version_id, id) select (worddetailsbyword(word)).* from words ) z
and analog
or better still:
select length(array_to_string(array_agg(output),'')) from ( with words as (select unnest(string_to_array(analysis_text,' ')) as word from verse where version_id = 3 and searchref between 857 and 879 order by version_id, id) select ((worddetailsbyword(word)).*)::text as output from words ) z
that way you can get an idea of any size difference in the data being transferred
.
also, do you need all the fields in (worddetailsbyword(word)).* ?
The Library
The Library