Re^3: DBI qw(:sql_types) with placeholders versus SQLite3

So I guess there is no way around creating a large query string on the fly, with or without place holders.

Well, you could simply create a temporary table with your big list of items in it and join against it. Let the DB take the strain - that's what it's there for.

🦛

Comment on Re^3: DBI qw(:sql_types) with placeholders versus SQLite3

Replies are listed 'Best First'.
Re^4: DBI qw(:sql_types) with placeholders versus SQLite3 by mldvx4 (Hermit) on Apr 01, 2024 at 11:04 UTC
I would have offloaded the work to the database but the integers in question are from an already complex query involving a three-way join, one of which is a self-join. I'm just barely familiar enough with SQL that I can write the query and do have to think a bit each time I re-examine it. However, if those results can be cached in a temporary table while still preserving the results of that original query, then I'll explore that option just in case. For right now, I like the readability of the Perl-side processing.	[reply]

Replies are listed 'Best First'.

Re^4: DBI qw(:sql_types) with placeholders versus SQLite3
by mldvx4 (Hermit) on Apr 01, 2024 at 11:04 UTC

I would have offloaded the work to the database but the integers in question are from an already complex query involving a three-way join, one of which is a self-join. I'm just barely familiar enough with SQL that I can write the query and do have to think a bit each time I re-examine it. However, if those results can be cached in a temporary table while still preserving the results of that original query, then I'll explore that option just in case. For right now, I like the readability of the Perl-side processing.

[reply]