@jimbojjz If you read about firstOrCreate it is looking for the first record in the DB...if it doesn't find one...it creates a new one. So, to answer your question, yes most would save the new record.
Save is not needed and matter of fact you are creating then updating. (Updating nothing) but if it finds the record it requires the save() method I believe. I generally use findOrNew instead.
FindOrCreate is good for like a user's profile after a new user hits their profile page. If the profile doesn't exist it will create a new one with defaults and return that object.
Where as find or new will not create but return a find object or a new empty class ready to manipulate
Yeah I had initially used firstOrNew() and might go back to it. I just was wondering if I was missing something obvious as I removed save() from firstOrCreate().