|
Lutha Mahtin posted:doobie??? sequel???? smoke two joins before you smoke two joins
|
# ? Sep 8, 2017 04:04 |
|
|
# ? May 25, 2024 04:32 |
|
what happened to my post, did the forums eat it edit: oh there it is
|
# ? Sep 8, 2017 04:07 |
|
Sapozhnik posted:Hmm? Explain, I'm curious. Always assumed FP alus were horribly complex beasts first of all, you'll notice that it's a pretty constrained format. we're not talking ieee 754 here. computers essentially multiply via long multiplication - to work out A * B, you work out A * 2, A * 4, A * 8 etc., and add together the ones that correspond to set bits in B. so the size of your multiplier is based on how large B could be (which dictates how many bits you might need to add together). if you wanted to support bitmaps up to 511x511, you'd need 9 bits, which means your multiplier would need to add together 9 different numbers. that's a huge amount of circuitry required! (the other option is to do the adding up over multiple cycles, re-using the same bits of circuitry, which is also complicated and still pretty big.) with this floating-point scheme, your multiplier only needs to add three different numbers, which is way smaller. then you just need a shifter on the front to apply the exponent, which is also pretty small.
|
# ? Sep 8, 2017 04:22 |
schranz kafka posted:they do, and we have to use Litmus for testing, and outlook is the worst poo poo of all of them. i'm using foundation framework for emails which is making it slightly less horrible, but not by much You're not on my team, are you? Cause yeah foundation, litmus, etc. The worst is exact target, really.
|
|
# ? Sep 8, 2017 04:41 |
|
Shaggar posted:its just gross to use a schemaless "database". it takes longer to develop with cause you have to manually handle all the validation and enforcement that a schema normally does. you also cant discover a schema so you have to basically document it externally which is totally stupid and error prone. use the dynamodb mapper library, or just use aurora my dude
|
# ? Sep 8, 2017 08:18 |
|
Luigi Thirty posted:i've got a weird problem here with C i know you solved this some other way, but just looking at it it looks like your MMIO32 macro is dereferencing the pointer, so it'd come out with type vuint32_t rather than vuint32_t *?
|
# ? Sep 8, 2017 09:22 |
|
holy poo poo jaguar is the best console
|
# ? Sep 8, 2017 12:21 |
|
Pie Colony posted:what i've generally found was PRs above a certain threshold of lines changed are just confusing, and the feedback received is more superficial (e.g. stylistic comments) than substantial (e.g. architectural comments). i basically try to never make PRs over ~150 lines, even if that means features are launched in a turned-off state. The commit was "enabled new warning and swept the codebase for it". Could it have been broken down? Yes. Would it be worth it? Maybe. ... Did I want to bother? Also, I had legitimate commits that once squashed down to atomic change had like 2k changed files and 10k changed lines. It couldn't have been split apart because it included a complete rework of how our build system resolved includes. We reviewed the hell out of the script automating the change though.
|
# ? Sep 8, 2017 14:08 |
|
If you ever write a book I promise to buy it. Terrible programmer SQL question - are triggers safe from race conditions? Like if you had... code:
|
# ? Sep 8, 2017 15:32 |
|
FamDav posted:use the dynamodb mapper library, or just use aurora my dude aurora is MySQL. I'm just gonna switch it to azure sql since its not much more expensive
|
# ? Sep 8, 2017 15:46 |
|
Shaggar posted:aurora is MySQL. I was going to say use the postgres version but it's still in open preview . I personally have no qualms with MySQL but that's more about spending too much time learning it's bs,
|
# ? Sep 8, 2017 15:53 |
|
tps: still writing groovy Result<Butt> result = getButt() // no error Butt butt = result.get() // GroovyCastException ahhhh
|
# ? Sep 8, 2017 16:27 |
|
gonadic io posted:tps: still writing groovy this seems bad, op
|
# ? Sep 8, 2017 16:30 |
|
it's almost like taking the type safety away from a language makes it worse?!?
|
# ? Sep 8, 2017 17:09 |
|
gonadic io posted:tps: still writing groovy why the only place I've met groovy is in gradle, and I only touch that when I absolutely can't get away with quietly using maven
|
# ? Sep 8, 2017 17:09 |
|
gonadic io posted:tps: still writing groovy what is one 'supposed' to do in this situation
|
# ? Sep 8, 2017 17:18 |
|
Legacy code. We're removing it slowly (apart from the times where we add a bunch to it for new features because they require parts we haven't moved out yet) fritz posted:what is one 'supposed' to do in this situation My code was actually correct, the problem was that the method getButt was defined like: Result<Butt> getButt(...) { Return new NotButt } Which was somehow not erroring and was succeeding fine until I tried to call any of butts methods So when I tried to assign NotButt to a Butt after the method call, I got the exception.
|
# ? Sep 8, 2017 17:27 |
|
fritz posted:what is one 'supposed' to do in this situation
|
# ? Sep 8, 2017 17:32 |
|
Wheany posted:holy poo poo jaguar is the best console Jaguar programming manual posted:Blitter Pointer Read Registers are at the wrong address
|
# ? Sep 8, 2017 17:46 |
|
lmao
|
# ? Sep 8, 2017 18:36 |
|
are you sure this console wasn't secretly designed by Microchip Technology
|
# ? Sep 8, 2017 18:37 |
|
toiletbrush posted:If you ever write a book I promise to buy it. Yay I get to be the first to respond! First this is a classic check-then-act race condition and running in a database doesn't save you. You need to follow the same design considerations as in other programming languages. It's simple to see how two simultaneous insert statements can pass the check at 9 records, and then both proceed with the insert, leaving you with 11 butts in the table. I think what you want is a Constraint Trigger that happens after the rows are inserted (but before it commits!), and rolls back that insert if there are more than 10 butts in the table. https://stackoverflow.com/questions/37277313/run-trigger-after-transaction-not-on-each-row-postgresql-9-4 Also read up on Transaction Isolation Levels which is another kind of concurrency issue particular to databases. http://www.oracle.com/technetwork/testcontent/o65asktom-082389.html
|
# ? Sep 8, 2017 20:01 |
|
I'm not entirely sure but I think that trigger should lock the table after an insert to do the reads for running the proc. Depending on whats in the proc you might cause a bunch of problems. a better solution is to use a check constraint to prevent the insert of a value over 10 or w/e you're trying to limit. whatever the question, triggers are never the answer.
|
# ? Sep 8, 2017 20:09 |
|
Sapozhnik posted:are you sure this console wasn't secretly designed by Microchip Technology it was designed by sinclair refugees and fabbed by IBM
|
# ? Sep 8, 2017 20:42 |
|
you should only use triggers to implement auto increment primary keys for your tables in Oracle everything else do in your app!!!!!!
|
# ? Sep 8, 2017 20:52 |
|
Valeyard posted:you should only use triggers to implement auto increment primary keys for your tables in Oracle You should only use triggers for the shotgun in your mouth after having to deal with Oracle databases
|
# ? Sep 8, 2017 21:19 |
|
moostaffa posted:You should only use triggers for the shotgun in your mouth after having to deal with Oracle databases
|
# ? Sep 8, 2017 22:39 |
|
moostaffa posted:You should only use triggers for the shotgun in your mouth after having to deal with Oracle databases
|
# ? Sep 8, 2017 22:51 |
|
moostaffa posted:You should only use triggers for the shotgun in your mouth after having to deal with Oracle databases content: there's no way we'd do use a trigger for what we need, we're using a check constraint, but it showed up in a stack overflow answer marked as 'correct' and my spidey sense tingled the moment I read it.
|
# ? Sep 8, 2017 23:18 |
|
trigger warning: oracle databases
|
# ? Sep 9, 2017 02:36 |
|
Valeyard posted:you should only use triggers to implement auto increment primary keys for your tables in Oracle please don't use auto-incrementing primary keys. Jesus didn't die for that
|
# ? Sep 9, 2017 02:50 |
|
FamDav posted:please don't use auto-incrementing primary keys. Jesus didn't die for that apologies for opening a potential can of worms here, but is this a more general argument against so-called surrogate keys or just an argument against auto-incrementing ones in particular? I'm db-curious but know nothing at the moment
|
# ? Sep 9, 2017 03:21 |
|
you can use an auto-increment and regret it later, or use a uuid and regret it now
|
# ? Sep 9, 2017 04:59 |
|
meatpotato posted:apologies for opening a potential can of worms here, but is this a more general argument against so-called surrogate keys or just an argument against auto-incrementing ones in particular? surrogate keys are the only correct option. never ever use natural keys. uuid keys are good and cool
|
# ? Sep 9, 2017 05:13 |
|
i have a personal project using sqlite and i think that that db has an auto increment int key column whether you like it or not. ill just ignore it because i just use the db here as a cache for web api data. but if i had to rely on teammates not using the auto int column i think my blood pressure would be in a worse state
|
# ? Sep 9, 2017 05:16 |
|
Sapozhnik posted:surrogate keys are the only correct option. never ever use natural keys. mega wrongo
|
# ? Sep 9, 2017 05:23 |
|
You should always prefer natural keys to surrogate keys. You should only use surrogate keys as a last resort. You will never have natural keys.
|
# ? Sep 9, 2017 06:13 |
|
you can just use the keying type that works as necessary or both
|
# ? Sep 9, 2017 07:51 |
|
what's so bad about uuids?
|
# ? Sep 9, 2017 08:31 |
|
|
# ? May 25, 2024 04:32 |
|
they don't fit neatly together if you're using them as a clustering key
|
# ? Sep 9, 2017 08:58 |