Implement script to create customer account for customer placed order before

[lcduong]

This PR is partly of this issue fossasia/eventyay-talk#166

Implement a script to create customer account for customer who placed order before.
By execute this script create_customer_account: python manage.py create_customer_account
then input organizer and event short name.

1. It will scan all the order of event.
2. detect order with email not have customer account
3. create customer account and link to that order
4. for order already have account, link that customer account to order as well

Summary by Sourcery

Add a script to create customer accounts for orders that do not have an associated customer account. The script scans all orders for a specified event and links existing customer accounts or creates new ones if necessary.

New Features:

• Introduce a management command to create customer accounts for orders without associated customer accounts.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request introduces a new management command script to create customer accounts for orders that do not have an associated customer account. The script takes organizer and event slugs as input, fetches the relevant orders, checks for existing customer accounts based on order emails, creates new customer accounts if necessary, and links the customer accounts to the orders.

File-Level Changes

Files	Changes
src/pretix/base/management/commands/create_customer_account.py	Added a new management command script to create customer accounts for orders without an associated customer account, including argument parsing, error handling, and logic to create and link customer accounts.

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sourcery-ai]

Hey @lcduong - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using database transactions to ensure atomicity of operations. This will prevent partial updates if the script fails midway.
• For better performance with large datasets, consider implementing batch processing for customer creation and order updates.

Here's what I looked at during the review

• 🟡 General issues: 4 issues found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.}

[sourcery-ai]

suggestion: Update the command's help text to accurately describe its functionality

The current help text doesn't match the command's actual functionality. Consider updating it to something like 'Create customer accounts for existing orders in an event'.

Suggested change

	help = 'Create SocialApp entries for Eventyay-ticket Provider'
	help = 'Create customer accounts for existing orders in an event'

[sourcery-ai]

suggestion: Replace sys.exit(1) with raising CommandError for better error handling

Using sys.exit(1) is not the recommended way to handle errors in Django management commands. Consider raising CommandError instead, which allows for better error reporting and doesn't abruptly terminate the process.

from django.core.management.base import CommandError

# ... (earlier in the code)

except Organizer.DoesNotExist:
    raise CommandError('Organizer not found.')
except Event.DoesNotExist:
    raise CommandError('Event not found.')

[sourcery-ai]

suggestion: Reconsider using email local part as full name

Using the email's local part as the full name might lead to inappropriate or nonsensical names. Consider using a placeholder like 'Unknown' or leaving it blank, allowing users to update it later.

Suggested change

	"full_name":order.email.split("@")[0]
	"full_name": "Unknown Customer"

[sourcery-ai]

suggestion (performance): Optimize database queries for better performance

For events with many orders, querying the database for each order could be slow. Consider optimizing by first fetching all unique emails from orders, then bulk creating customers for emails without accounts.

Suggested change

	for order in orders:
	unique_emails = orders.values_list('email', flat=True).distinct()
	existing_customers = set(Customer.objects.filter(email__in=unique_emails).values_list('email', flat=True))
	new_customers = [Customer(email=email) for email in unique_emails if email and email not in existing_customers]
	Customer.objects.bulk_create(new_customers)

[norbusan]

Looks fine to me, although the suggestions by sourcery-ai also sound reasonable