Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "Theo - t3․gg" channel.

There doesn’t seem to be such a thing as a “NoSQL” DBMS any more. Even nonrelational DBMSes are adopting a form of SQL for their query language.
3
I don’t understand why a proprietary vendor-specific feature like “Intellisense” is grounds for declaring that a cross-platform standard is somehow deficient. Clearly the deficiency lies in the proprietary product.
1
@blazinghellwheels If you don’t want to have the option of NULL values, you don’t have to. I have found them quite useful myself. Even on fields that aren’t supposed to have NULL values.
1
@blazinghellwheels The reason why I mention NULL values in fields that aren’t supposed to have them is they can occur when doing something like a left join: a NULL in what is supposed to be the primary key of a joined table, for example, indicates that the whole record is absent. How would you represent such a situation without NULL?
1
I call it esskewell. And its most popular implementation as ess-kew-lite.
1
With Python, it’s a very powerful combination. Here’s the sort of dynamic query criterion I have constructed: list ( "%(name)s like %(value)s" % { "name" ∶ field[0], "value" ∶ sqlstring("%" + escape_sql_wild(params․getvalue(field[1])) + "%"), } for field in ( ("make", "search_make"), ("model", "search_model"), ("details", "search_details"), ("serial_nr", "search_serial"), ("inventory_nr", "search_invent"), ("requisition_nr", "search_requis"), ("machine_name", "search_machine_name"), ("os_updates", "search_os"), ) if params․getvalue(field[1]) != "" )
1