32a3a No.2198
>>2188>lowercase everything because uppercase headers always mess up my sql queries later onlowercasing is a lifesaver, but watch out for when that regex accidentally eats the
only distinguishing character in some weirdly named column and leaves you with two identical headers.
32a3a No.2205
>>2198 happened to me with a client export where 'id_v1' and 'id-v1' both became
just id and broke my whole migration script.
32a3a No.2215
>>2188>lowercase everything because uppercase headers always mess up my sql queries later onI actually find that keeping some casing helps me spot things like
User_ID vs
user_id when I'm debugging. It makes it way easier to see if a column is a primary key or just some random attribute at a glance.