Subjunctive posted:

I think they accidentally used gwt for something once, before they realized it was theirs and stopped.

Jabor posted:

A bunch of internal tooling uses angular (actually, internal products tend to be more early-adopter than customer-facing products in general), but there's also stuff like leanback and doubleclick.

Subjunctive posted:

does Google use Angular (either version) for anything important?

Subjunctive posted:

that's interesting. I think our first major users of react were a) the mostly widely used page on our site, news feed, and b) the customer-facing tools through which most of our money comes in, ad management. I don't know how hard it is to use angular as part of something (like a new gmail widget or some part of news); that aspect of react really helped accelerate adoption, because if we'd had to convert all of news feed to react before we deployed any of it lolwutimo.

MALE SHOEGAZE posted:

hey can you get the person responsible for this to pay for my therapy? tia



"okay sure i'll just configure my endpoints and not wor-"





(of course what would be the point of maintaining legacy endpoints while updating the schema? still though ugh)

Shaggar posted:

idk much about reporting but these kinds of tables are pretty common I guess? basically they want Business ID - Reporting Year to be a filter and then you have an id for that filter to make it easy to work w/

but yeah you want an auto increment identity column and then columns for the business area id and reporting year. pk is the auto increment id and then a unique key on business area id + reporting year.

Then use something like

SQL code:

INSERT INTO BusinessAreaReportingYears (BusinessAreaId, ReportingYear)
SELECT 
	BusinessAreaId
	,DATEPART(year,GETDATE())
FROM
	BusinessAreas

to load the table. You will want to load it once a year or you could prefill it with years forever, but you would need to keep it updated as new business areas are added.

Snapchat A Titty posted:

also lol at my stupid hash function

code:

var hashValue: Int { return self.x * 1000 + self.y; }

uncurable mlady posted:

shags, whats your beef with EF anyway

~Coxy posted:

i don't think this would work due to the requirement to have incrementing IDs per year and business area
in fact I can't think of a way to meet that reqt using PKs, without doing something dumb like multiple tables

you're going to need to generate the PK on insert in the app layer, or using a trigger or something

rrrrrrrrrrrt posted:

angular is a spa framework so it really isn't meant to be used for small pieces or widgets or w/e. not that you couldn't it just doesn't make a lot of sense. not the way it would for something like react at least.

triple sulk posted:

one of these places I've been talking to said they were rewriting their api from webapi to node and short of new(ish) hotness I have no idea why. also they described their culture (when I asked about how they work, generally speaking) as a "war room" which I assume means 80 hour work weeks

fleshweasel posted:

seems to me like letting a bunch of different apps have raw access to a database makes for more code churn if you need to change schema. better to give those apps access to the same API for doing database stuff. it's like providing clients with an interface as opposed to handing them an implementation.

rrrrrrrrrrrt posted:

do you HAVE to let EF own your schema? or is it like hibernate where you can develop your model entirely independently and wrap hibernate around it? i was on a team once that was creating their db exclusively by reverse engineering their hibernate model and good lord is was the worst pos imaginable.

rrrrrrrrrrrt posted:

do you HAVE to let EF own your schema?

Shaggar posted:

yeah your procs are the interface between your application and the database. in fact when using a statement mapper its common to create an actual interface with methods that will be used for data access and then have the statement mapper bind the inputs and outputs from the interface methods to statements/procs. w/ spring mybatis this can be done automatically with the resulting proxy injected into wherever you want. its the best way to do data access by far.

Shaggar posted:

yeah your procs are the interface between your application and the database. in fact when using a statement mapper its common to create an actual interface with methods that will be used for data access and then have the statement mapper bind the inputs and outputs from the interface methods to statements/procs. w/ spring mybatis this can be done automatically with the resulting proxy injected into wherever you want. its the best way to do data access by far.

Subjunctive posted:

shaggar was exactly right

Soricidus posted:

Shaggar posted:

I've used table valued functions before, but I always end up going another way usually cause it ends up not being that reusable.

also theres a lot of fud about performance in sql and most of it comes down to people not being able to separate certain patterns from poor performance caused by implementation. like if you have a function that is internally joining to a bunch of tables and then you include that function in a join somewhere else then yes of course that's going to be slow you idiot. but if your function is just concatenating strings or something then that will be plenty fast.

SQL server is generally pretty good at optimizing queries and a function containing the same code as something you're coping and pasting around should have the same performance (for the most part).

also CTEs are gr8

Malcolm XML posted:

index inDEX INDEX

Shaggar posted:

"hrm, why is this query so slow?"

"well whats the index on?"

"index?"

Subjunctive posted:

that's interesting. I think our first major users of react were a) the mostly widely used page on our site, news feed, and b) the customer-facing tools through which most of our money comes in, ad management. I don't know how hard it is to use angular as part of something (like a new gmail widget or some part of news); that aspect of react really helped accelerate adoption, because if we'd had to convert all of news feed to react before we deployed any of it lolwutimo.

MALE SHOEGAZE posted:

angular is bad for every use case except for making gmail

Subjunctive posted:

wait what? no WAY do they use angular for gmail.

MALE SHOEGAZE posted:

in other news i spent hours today getting an animated tayne to dance around in the terminal while gradlew/spring is spinning up.

it forks the spring boot process and then when the app bootstraps it sends a sighup to tayne.pid.

but the part i spent like 3 hours on was trying to get io redirection to work such that the spring logs wouldnt gently caress up taynes dancing. couldn't figure that out

i think tomorrow i'm gonna dockerize it completely

bobbilljim posted:

a good use of time.

MALE SHOEGAZE posted: